Error hanlind with BDC Call Transation

Hi SAP Minds,
I have done the BDC for SU01 with recording method.Used CALL TRANSACTION method, but can any one guide me how to capture the errors into internal table IT_BDCMSGCOLL.
Please assist me.

Hi,
call transaction 'TCODE' using bdcdata mode 'MODE'
update 'UPDATE' messages into it_bdcmsgcoll.
After the call transaction errors are in the it_bdcmsgcoll table
a®

Similar Messages

Error Records in BDC Call transaction

Hi.....
     I am new to BDC concept... Can any of u tell me how to collect error records in BDC Call transaction... I already collected error messages through BDCMSGCOL... but i dont know how to collect those error records... here i am using two different flat files for header and line item... and kindly tell me if there is an error in line item how to get it so with relevent header details...
thanks,

Hi,
      LOOP AT t_bdcmsgcoll INTO w_bdcmsgcoll.
        PERFORM f_format_msg USING w_bdcmsgcoll CHANGING w_return.
     ENDLOOP.
Form format_msg
DATA : l_mstring(480).
CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
      id        = w_bdcmsgcoll-msgid
      lang      = w_bdcmsgcoll-msgspra
      no        = w_bdcmsgcoll-msgnr
      v1        = w_bdcmsgcoll-msgv1
      v2        = w_bdcmsgcoll-msgv2
      v3        = w_bdcmsgcoll-msgv3
      v4        = w_bdcmsgcoll-msgv4
    IMPORTING
      msg       = l_mstring
    EXCEPTIONS
      not_found = 1
      OTHERS    = 2.
End format_msg
you can use the l_mstring to process further and pass to the bapiret2 table
Regards,
Vijaya

Error Capturing in BDC Call Transaction Method

How does the Errors in BDC Call Transactin is captured ....can you please give same examples of using BDCMSGCOLL and FORMAT_MESSAGES..
Please explain clearly when to used these in real time..
Thankyou

hi,
Here is hte sample code
        call transaction 'ME22' using it_bdc
                options from x_ctu_params
                messages into lt_message.
       clear w_success.
       if sy-subrc <> 0.
       w_success = 'N'.
       endif.
        loop at lt_message where msgtyp = 'E' or
                                 msgtyp = 'A'.
        endloop.
        if sy-subrc = 0.
          perform format_messages tables lt_message
                                  using lv_msg lv_lines.
*         To append error messages
          perform append_message tables lt_message
                                        return
                                 using lv_msg.
        else.
          if w_success = 'N'.
          perform format_messages tables lt_message
                                  using lv_msg lv_lines.
          perform append_message_err tables lt_message
                                        return
                                 using lv_msg.
          else.
          perform format_messages tables lt_message
                                  using lv_msg lv_lines.
*         To append success messages
          perform append_message tables lt_message
                                        return
                                 using lv_msg.
          endif.
        endif.
        refresh: it_bdc,
                 lt_message.
      endat.
    endloop.
endif.
form format_messages tables pt_messages structure bdcmsgcoll
                     using   pv_msg pv_lines.
clear : pv_lines,pt_messages,pv_msg.
describe table pt_messages lines pv_lines.
read table pt_messages index pv_lines.
check not pt_messages-msgid is initial.
*-- Function module to format the message given
call function 'FORMAT_MESSAGE'
       exporting
            id        = pt_messages-msgid
            lang      = sy-langu
            no        = pt_messages-msgnr
            v1        = pt_messages-msgv1
            v2        = pt_messages-msgv2
            v3        = pt_messages-msgv3
            v4        = pt_messages-msgv4
       importing
            msg       = pv_msg
       exceptions
            not_found = 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 into pv_msg.
endif.
endform.                    " format_messages
Regards,
Richa

Reprint the processed order with BDC call transaction

Hi Mentors,
I have a problem with printing the order which is coming in a cockpit program.
for that i am using the bdc and call transaction 'ZVA31' which is exactly the standard program 'SD70AV1A'.
but after first processing i am not able to reprint the processed order.
Below is my bdc code and i am using processing mode 1 at the time of recording.
FORM ZSD70AV1A_PRINT_BA01 USING p_vbeln TYPE vbeln.
DATA: wa_ba01 TYPE nast-kschl VALUE 'BA01'.
perform bdc_dynpro      using 'SD70AV1A' '1000'.
perform bdc_field       using 'BDC_CURSOR'
'RG_KSCHL-LOW'.
perform bdc_field       using 'BDC_OKCODE'
'=ONLI'.
perform bdc_field       using 'RG_KSCHL-LOW'
wa_ba01."wa_ba01."'ba01'.
perform bdc_field       using 'PM_NSORT'
'01'.
perform bdc_field       using 'PM_VERMO'
'1'.
perform bdc_field       using 'RG_VBELN-LOW'
p_vbeln."'513785'.
perform bdc_dynpro      using 'SAPMSSY0' '0120'.
perform bdc_field       using 'BDC_CURSOR'
'04/03'.
perform bdc_field       using 'BDC_OKCODE'
'=&ALL'.
perform bdc_dynpro      using 'SAPMSSY0' '0120'.
perform bdc_field       using 'BDC_CURSOR'
'04/03'.
perform bdc_field       using 'BDC_OKCODE'
'=PROC'.
CALL TRANSACTION 'ZVA31' USING BDCDATA
MODE   'A'
MESSAGES INTO MESSTAB.
CLEAR BDCDATA[].
ENDFORM.                    " ZSD70AV1A_PRINT_BA01
Br,
Surya

Solved myself.
DATA: wa_ba00 TYPE nast-kschl VALUE 'BA00'.
DATA: p_vermo TYPE kschl.
DATA: cur_vstat TYPE nast-vstat.
SELECT SINGLE vstat INTO cur_vstat FROM nast
WHERE objky = p_vbeln
AND   kschl = 'BA00'.
IF sy-subrc = 0 AND cur_vstat = 0.
p_vermo = '1'."wa_vstat.
ELSE.
p_vermo = '2'.
ENDIF.
p_vermo is processing status.
Br,
Surya

How can we update mk01 with BDC call transaction method

can any one send the sample code for upload of MK01 using call transaction method.
its urgent..

Use the following code.
*& Report ZMK01_VA01                                                  *
REPORT Z_MK01                              .
SOURCE INTERNAL TABLE
DATA: BEGIN OF T_SOURCE OCCURS 0,
        LIFNR TYPE LIFNR,
        EKORG TYPE EKORG,
        KTOKK TYPE KTOKK,
        NAME1 TYPE NAME1,
        SORTL TYPE SORTL,
        LAND1 TYPE LAND1,
        WAERS TYPE WAERS,
      END OF T_SOURCE.
*DATA: E_MESSAGE TYPE C.
ERROR MESSAGE TABLE
DATA: T_ERRORMSG LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
TARGET TABLE LIKE BDCDATA
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
TO UPLOAD DATA FROM LEGACY SYSTEM
      CALL FUNCTION 'WS_UPLOAD'
EXPORTING
        CODEPAGE                      = ' '
         FILENAME                      = 'D:\MK01.TXT'
         FILETYPE                      = 'DAT'
      IMPORTING
        FILELENGTH                    =
        TABLES
          data_tab                      = T_SOURCE
       EXCEPTIONS
         CONVERSION_ERROR              = 1
         FILE_OPEN_ERROR               = 2
         FILE_READ_ERROR               = 3
         INVALID_TYPE                  = 4
         NO_BATCH                      = 5
         UNKNOWN_ERROR                 = 6
         INVALID_TABLE_WIDTH           = 7
         GUI_REFUSE_FILETRANSFER       = 8
         CUSTOMER_ERROR                = 9
         NO_AUTHORITY                  = 10
         OTHERS                        = 11
      IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
TRANSFERING DATA FROM INTERNAL SOURCE TABLE TO TARGET TABLE
LOOP AT T_SOURCE.
REFRESH BDCDATA.
perform bdc_dynpro      using 'SAPMF02K' '0107'.
perform bdc_field       using 'BDC_CURSOR'
                              'RF02K-LIFNR'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'RF02K-LIFNR'
                              T_SOURCE-LIFNR.
perform bdc_field       using 'RF02K-EKORG'
                              T_SOURCE-EKORG.
perform bdc_field       using 'RF02K-KTOKK'
                              T_SOURCE-KTOKK.
perform bdc_dynpro      using 'SAPMF02K' '0110'.
perform bdc_field       using 'BDC_CURSOR'
                              'LFA1-LAND1'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'LFA1-NAME1'
                              T_SOURCE-NAME1.
perform bdc_field       using 'LFA1-SORTL'
                              T_SOURCE-SORTL.
perform bdc_field       using 'LFA1-LAND1'
                              T_SOURCE-LAND1.
perform bdc_dynpro      using 'SAPMF02K' '0120'.
perform bdc_field       using 'BDC_CURSOR'
                              'LFA1-KUNNR'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_dynpro      using 'SAPMF02K' '0310'.
perform bdc_field       using 'BDC_CURSOR'
                              'LFM1-WAERS'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'LFM1-WAERS'
                              T_SOURCE-WAERS.
perform bdc_dynpro      using 'SAPMF02K' '0320'.
perform bdc_field       using 'BDC_CURSOR'
                              'RF02K-LIFNR'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_dynpro      using 'SAPLSPO1' '0300'.
perform bdc_field       using 'BDC_OKCODE'
                              '=YES'.
CALL TRANSACTION 'MK01' USING BDCDATA MODE 'A' MESSAGES INTO T_ERRORMSG.
ENDLOOP.
LOOP AT T_ERRORMSG.
WRITE:/ 'MESSAGE TYPE',T_ERRORMSG-MSGTYP,
         'FIELDNAME WERE ERROR OCCURED', T_ERRORMSG-FLDNAME.
*CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
ID              = T_ERRORMSG-MSGID
LANG            = SY-LANGU
NO              = T_ERRORMSG-MSGNR
V1              = T_ERRORMSG-MSGV1
V2              = T_ERRORMSG-MSGV2
V3              = T_ERRORMSG-MSGV3
V4              = T_ERRORMSG-MSGV4
IMPORTING
MSG             = E_MESSAGE
EXCEPTIONS
NOT_FOUND       = 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.
*WRITE:/ E_MESSAGE.
ENDLOOP.
       Start new screen                                              *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO   = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.
       Insert field                                                  *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> SPACE.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
ENDIF.
ENDFORM.
With Regards
K Srinivas

Error in BDC CALL TRANSACTION METHOD..

hai i got an error in doing BDC CALL TRANSACTION METHOD
Error:diffrent number of parameters in FORM and PERFORM(routine :FILL_SCREEN_DETAILS:,number of formal parameters :3,number of actual parameters:1)
PROGRAM
REPORT ZDEMO_UPLOAD_COST_CENTER_DATA.
DATA:BEGIN OF WA_DATA,
KOKRS TYPE KOKRS,"CONTROLLING AREA
KOSTL TYPE KOSTL,"COST CENTER
DATAB TYPE DATAB,"START DATE
DATBI TYPE DATBI,"END DATE
KTEXT TYPE KTEXT,"NAME
LTEXT TYPE LTEXT,"DESCRIPTION
VERAK TYPE VERAK,"PERSON RESPONSIBLE
KOSAR TYPE KOSAR, "COST CENTER CATEGORY
KHINR TYPE KHINR,"HIERARCHY AREA
BUKRS TYPE BUKRS,"COMPANY CODE
GSBER TYPE GSBER,"BUISINESS AREA
END OF WA_DATA.
*TYPES:IT_DATA TYPE STANDARD TABLE OF TY_DATA.
DATA:IT_DATA LIKE TABLE OF WA_DATA,
      IT_BDCDATA LIKE TABLE OF BDCDATA,
      WA_BDCDATA LIKE LINE OF IT_BDCDATA,
      IT_BDCMSGCOLL LIKE TABLE OF BDCMSGCOLL,
      WA_BDCMSGCOLL LIKE LINE OF IT_BDCMSGCOLL.
DATA :V_FILE TYPE STRING.
CONSTANTS :C_KS01(4) TYPE C VALUE 'KS01',
            C_X(1) TYPE C VALUE 'X',
            C_A(1) TYPE C VALUE 'A'.
SELECTION-SCREEN:BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETER :PA_FILE LIKE FC03TAB-PL00_FILE OBLIGATORY.
SELECTION-SCREEN:END OF BLOCK B1.
*AT SELECTION SCREEN ON VALUE REQUEST
* EVENT TO BE TRIGGERED WHEN WE PRESS F4.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR PA_FILE.
PERFORM GET_F4_FOR_FILE USING PA_FILE.
*         START-OF-SELECTION
START-OF-SELECTION.
*WE NEED TO MOVE THE PA_FILE INTO ANOTHER VARIABLE OF TYPE STRING
*AS WE ARE GOING TO USE THE SAME IN THE FM:GUI_UPLOAD THERE THE FILE TYPE IS STRING
V_FILE = PA_FILE.
PERFORM UPLOAD_FILE_T0_ITAB USING V_FILE CHANGING IT_DATA.
*FILL THE SCREEN AND FIELD DETAILS
LOOP AT IT_DATA INTO WA_DATA.
REFRESH IT_BDCDATA.
*FIRST SCREEN DETAILS
PERFORM FILL_SCREEN_DETAILS USING 'SAPLKMA1''0200''X'.
*CURSOR DETAILS
PERFORM FILL_FIELD_DETAILS USING 'BDC_CURSOR''CSKSZ-KOKRS'.
*OK CODE DETAILS
PERFORM FILL_FIELD_DETAILS USING 'BDC_OKCODE''/00'.
*CONTROLLING AREA
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-KOKRS' WA_DATA-KOKRS.
*COST CENTER DETAILS
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-KOSTL' WA_DATA-KOSTL.
* START DATE
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-DATAB_ANFO' WA_DATA-DATAB.
*END DATE
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-DATBI_ANFO' WA_DATA-DATBI.
*NEXT SCREEN DETAILS
PERFORM FILL_SCREEN_DETAILS USING 'SAPLKMA1''0299''X'.
*OKCODE DETAILS
PERFORM FILL_FIELD_DETAILS USING 'BDC_OKCODE''=BU'.
*SUBSCRN FIELD DETAILS
PERFORM FILL_FIELD_DETAILS USING 'BDC_SUBSCR''BDC-SUBSCR'.
*CURSOR DETAILS
PERFORM FILL_FIELD_DETAILS USING 'BDC_CURSOR''CSKSZ-WAERS'.
*NAME
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-KTEXT' WA_DATA-KTEXT.
*DESCRIPTION
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-LTEXT' WA_DATA-LTEXT.
*PERSON RESPONSIBLE
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-VERAK' WA_DATA-VERAK.
*COST CENTER CATEGORY
PERFORM FILL_FIELD_DETAILS USING'CSKSZ-KOSAR' WA_DATA-KOSAR.
*HIERARCHY AREA
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-KHINR' WA_DATA-KHINR.
*COMPANY CODE
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-BUKRS' WA_DATA-BUKRS.
*BUISINESS AREA
PERFORM FILL_FIELD_DETAILS USING 'CSKSZ-GSBER' WA_DATA-GSBER.
*CALL THE TRANSACTION
CALL TRANSACTION C_KS01 USING IT_BDCDATA
                          MODE C_A "ALL SCREENS
                                   "N-NO SCREENS
                                   "E-ERROR SCREENS ONLY
                          UPDATE 'A' "ASYNCHRONOUS
                                      "SYNCHRONOUS
                          MESSAGES INTO IT_BDCMSGCOLL.
ENDLOOP.
* FORM FILL SCREEN_DETAILS
FORM FILL_SCREEN_DETAILS USING PROGRAM LIKE BDCDATA-PROGRAM
                       DYNPRO LIKE BDCDATA-DYNPRO
                       DYNBEGIN LIKE BDCDATA-DYNBEGIN.
CLEAR WA_BDCDATA.
WA_BDCDATA-PROGRAM = PROGRAM.
WA_BDCDATA-DYNPRO = DYNPRO.
WA_BDCDATA-DYNBEGIN = DYNBEGIN.
APPEND WA_BDCDATA TO IT_BDCDATA.
ENDOFRM.
* FORM FILL_FIELD_DETAILS
FORM FILL_FIELD_DETAILS USING FNAM FVAL.
CLEAR WA_BDCDATA.
WA_BDCDATA-FNAM = FNAM.
WA_BDCDATA-FVAL = FVAL.
APPEND WA_BDCDATA TO IT_BDCDATA.
ENDFORM.
* FORM GETE_F4_FOR_FILE
*DISPLAY ALL THE FILES IN THE SYSTEM FOR SELECTION
*P_PA_FILE NAME OF THE FILE
FORM GET_F4_FOR_FILE USING P_PA_FILE.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
* EXPORTING
*    PROGRAM_NAME        = SYST-REPID
*    DYNPRO_NUMBER       = SYST-DYNNR
    FIELD_NAME          = 'PA_FILE'
*    STATIC              = ' '
*    MASK                = ' '
   CHANGING
     FILE_NAME           = PA_FILE.
* EXCEPTIONS
*    MASK_TOO_LONG       = 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.
* FORM UPLOAD_FILE_TO_ITAB
* FP_V_FILE = FILE NAME
*FP_IT_DATA = INTERNAL TABLE TO STORE THE DATA
FORM UPLOAD_FILE_TO_ITAB USING FP_V_FILE CHANGING FP_IT_DATA LIKE IT_DATA.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    FILENAME                      = FP_V_FILE
HAS_FIELD_SEPARATOR           = ' X'
TABLES
    DATA_TAB                      =FP_IT_DATA.
ENDFORM.
Edited by: saifudheenc on Aug 7, 2010 5:09 PM

hi
try to add spaces between parameters :
example:
PERFORM FILL_SCREEN_DETAILS USING 'SAPLKMA1' '0200' 'X'.
regards,darek

Error While Uploading Material Master Through Bdc Call Transaction

Hi Sap Gurus,
I am doing Bdc call Transaction for Material Master Uploading.
But After Entering data for 4-5 screen i got a error_
Field Mara-iprkz doesn,t exit in the screen saplmgmm 4000
Field Mara-prctr doesn,t exit in the screen saplmgmm 4000
Field Mbew-stprs doesn,t exit in the screen saplmgmm 4000
Field Marc-mtvfe doesn,t exit in the screen saplmgmm 4000
Enter Valuation class.
This is my Programme....................................
<removed by moderator>
Thanks in advance.
Arindam
Moderator message: please post only relevant code parts, your post must be less than 5000 characters to preserve formatting.
Edited by: Thomas Zloch on Apr 16, 2011 9:29 PM

Sorry for my obvious answer, but you should ask a more precise question.
Your errors are that you try to enter fields but they don't exist, so it sounds logic.
And the error "Enter Valuation class." means that the field is mandatory. So you must enter it.
Re-record the transaction using SHDB (eventually play with the http://wiki.sdn.sap.com/wiki/display/ABAP/Recordduringplay), run it in A display mode, and correct your program.
Sandra
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'MVKE-SKTOF'
                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'MARC-PRCTR'
                              wa_mara-prctr."'MUMBAI'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'MARA-IPRKZ'
                              'D'.

Error handling in bdc Fb01along with erros in Idoc.

Hi,
Can any one send me the sample code for the error handling in bdc Fb01along with erros in Idoc. Actually, mail should be sent
Thanks
Avi.

Hi,
This may help you.
<b>FORM send_mail USING   receiver.
CLEAR: w_lines,tbl_packing_list,tbl_object_header,
             tbl_contents_txt, tbl_receivers.
REFRESH:tbl_packing_list, tbl_object_header,
           tbl_contents_txt,tbl_receivers.
SORT tbl_err.
DELETE ADJACENT DUPLICATES FROM tbl_err COMPARING ALL FIELDS.
IF NOT tbl_err[] IS INITIAL.
Preparing the email.
    PERFORM prepare_email.
ELSE.
   If sy-subrc NE 0.
      MOVE sy-subrc TO w_code.
   ENDIF.
    EXIT.
ENDIF.
Get the content of header e-mail document data
PERFORM document_data.
Get details of the error file attached (like type of file and format)
PERFORM packing_list.
Get receiver mail id's
tbl_receivers-receiver = receiver.
tbl_receivers-rec_type = 'C'.
tbl_receivers-express = c_flag.
tbl_receivers-sap_body = c_flag.
APPEND tbl_receivers.
Call FM to send E-mails to receivers
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
       EXPORTING
            document_data              = st_document_data
            put_in_outbox              = 'X'
       TABLES
            packing_list               = tbl_packing_list
            object_header              = tbl_object_header
            contents_txt               = tbl_contents_txt
            receivers                  = tbl_receivers[]
       EXCEPTIONS
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            OTHERS                     = 8.
ENDFORM.                    " send_mail
*&      Form prepare_email
      text
--> p1        text
<-- p2        text
FORM prepare_email.
E-Mail body content
IF NOT w_lifnr IS INITIAL.
    CONCATENATE text-015 w_docnum text-016
           INTO tbl_contents_txt-line
      SEPARATED BY space.
ENDIF.
APPEND tbl_contents_txt.
CLEAR tbl_contents_txt.
E-mail error file attachment header
CONCATENATE text-063 text-064
               text-065 text-066 c_comma
         INTO tbl_contents_txt-line
    SEPARATED BY c_comma.
APPEND tbl_contents_txt.
CLEAR tbl_contents_txt.
E-mail error file attachment content
LOOP AT tbl_err.
    CONCATENATE w_docnum tbl_err-v_segnum
                tbl_err-msg tbl_err-type
      INTO tbl_contents_txt-line
      SEPARATED BY c_comma.
    CONCATENATE c_linefeed tbl_contents_txt-line c_comma
           INTO tbl_contents_txt-line.
    APPEND tbl_contents_txt.
    CLEAR tbl_contents_txt.
ENDLOOP.
ENDFORM.                    " prepare_email
*&      Form document_data
      text
--> p1        text
<-- p2        text
FORM document_data.
CLEAR w_line.
IF NOT w_lifnr IS INITIAL.
    CONCATENATE text-075 text-027 sy-datum sy-uzeit INTO w_line
    SEPARATED BY c_uscore.
ENDIF.
st_document_data-obj_name = w_line.
st_document_data-obj_descr = w_line.
st_document_data-priority = 1.
st_document_data-obj_prio = 1.
ENDFORM.                    " document_data
*&      Form packing_list
      text
--> p1        text
<-- p2        text
FORM packing_list.
CLEAR w_lines.
DESCRIBE TABLE tbl_err LINES w_lines.
READ TABLE tbl_contents_txt INDEX w_lines.
tbl_packing_list-head_start = 1.
tbl_packing_list-head_num   = 1.
tbl_packing_list-body_start = 1.
tbl_packing_list-body_num   = 1.
tbl_packing_list-doc_type   = 'RAW'.
APPEND tbl_packing_list.
tbl_packing_list-head_start = 1.
tbl_packing_list-head_num   = 0.
tbl_packing_list-body_start = 2.
tbl_packing_list-body_num   = w_lines + 1.
tbl_packing_list-doc_type   = 'CSV'.
tbl_packing_list-obj_descr = 'Error_Attachment'(060).
IF NOT w_lifnr IS INITIAL.
    tbl_packing_list-obj_name   = 'Idoc Number is'(072).
ENDIF.
tbl_packing_list-doc_size   = 255 * ( w_lines + 1 ).
APPEND tbl_packing_list.
ENDFORM.                    " packing_list
</b>
Thanks
Manju.

Plz tell me BDC CALL TRANSACTION steps with simple example

hi,
plz tell me the steps
BDC CALL TRANSACTION steps with simple example

Hi,
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
? The first is when application data to be replaced is transferred at once, and only once.
? The second situation is to transfer data periodically from external systems to SAP and vice versa.
? There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called ?batch input? or ?batch data communication?.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a ?data transfer? program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
? To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
? To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
? The transaction code, if you do not already know it.
? Which fields require input i.e., mandatory.
? Which fields can you allow to default to standard values.
? The names, types, and lengths of the fields that are used by a transaction.
? Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
? Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System ? Status.)
? Step through the transaction, entering the data will be required for processing your batch input data.
? On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
? Display these by choosing System ? Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
? For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which you?ll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
? Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
? Create a BDCDATA structure
? Write the structure out to a session or process it with CALL TRANSACTION USING; and then
? Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
? Data that is entered into screen fields.
? Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
? PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
? DYNPRO: Screen Number. Set this field only in the first record for the screen.
? DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to ? ? (blank) for all other records.)
? FNAM: Field Name. The FNAM field is not case-sensitive.
? FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
? User Name: User name
? Group: Name of the session
? Lock Date: The date on which you want to process the session.
? Keep: This parameter is passed as ?X? when you want to retain session after
processing it or ? ? to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
? Tcode: Transaction Name
? Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter ? 1 is transaction code.
Parameter ? 2 is name of BDCTAB table.
Parameter ? 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter ? 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter ? 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
Thanks &regards,
Sravani

Please help with BDC error

Hello guys,
I recently modified a BDC program and I configured it's mode to be 'E' so when errors are present,pop up windows are shown. Unfortunately I can't seem to find the error. I will post below the code. What I did with the code was to clear the value of anep-anbtr to no value. help would really be appreciated. Thanks guys!
FORM GENERATE_BDC_DATA_ABAA.
DATA: I_ANBTR LIKE ANEP-ANBTR.
DATA: C_ANBTR(16), C_ANBTR2(16), C_DMBTR(16).
PERFORM BDC_DYNPRO USING 'SAPMA01B' '0100'.
PERFORM BDC_FIELD USING:
      'BDC_OKCODE' '/00',
      'ANBZ-BUKRS' 'GLOB',
      'ANBZ-ANLN1' IT_REC-ANLN1,
      'ANBZ-ANLN2' IT_REC-ANLN2,
      'ANEK-BLDAT' IT_REC-BLDAT,
      'ANEK-BUDAT' IT_REC-BUDAT,
      'ANBZ-PERID' IT_REC-PERID,
      'ANBZ-BWASL' IT_REC-BWASL.
PERFORM BDC_DYNPRO USING 'SAPMA01B' '0110'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '/00'.
PERFORM BDC_FIELD USING 'ANBZ-DMBTR' IT_REC-DMBTR.
PERFORM BDC_FIELD USING: 'ANBZ-BZDAT' IT_REC-BUDAT,
                            'ANEK-SGTXT' IT_REC-SGTXT.
"I_ANBTR = '0'.       "IT_REC-DMBTR * -1.
perform bdc_dynpro      using 'SAPMA01B' '0285'.          " '0600'.
*AVH
clear anep-anbtr.
perform bdc_field       using 'BDC_CURSOR'
                                'ANEP-ANBTR'.
perform bdc_field       using 'BDC_OKCODE'
                                '=AUSF'.
*AVH
clear anep-anbtr.
PERFORM BDC_DYNPRO USING 'SAPMA01B' '0285'.               " '0600'.
*AVH
clear anep-anbtr.
PERFORM BDC_FIELD USING 'BDC_CURSOR' 'ANEP-ANBTR'.
PERFORM BDC_FIELD USING 'BDC_OKCODE' '=AUSF'.
PERFORM BDC_FIELD USING 'ANEP-ANBTR' '0'.
*AVH
clear anep-anbtr.
PERFORM BDC_DYNPRO USING 'SAPMA01B' '0110'.
PERFORM BDC_FIELD USING:
      'BDC_OKCODE' '=UPDA',
      'ANBZ-DMBTR' IT_REC-DMBTR,
      'ANBZ-BZDAT' IT_REC-BUDAT,
      'ANEK-SGTXT' IT_REC-SGTXT.
PERFORM BDC_DYNPRO USING 'SAPMA01B' '0285'.               " '0600'.
*AVH
clear anep-anbtr.
PERFORM BDC_FIELD USING:
      'BDC_CURSOR' 'ANEP-ANBTR',
      'BDC_OKCODE' '=AUSF'.
PERFORM BDC_FIELD USING 'ANEP-ANBTR' '0'.
*AVH
clear anep-anbtr.
PERFORM BDC_DYNPRO USING 'SAPMA01B' '0285'.               " '0600'.
*AVH
clear anep-anbtr.
PERFORM BDC_FIELD USING:
      'BDC_CURSOR' 'ANEP-ANBTR',
      'BDC_OKCODE' '=AUSF'.
PERFORM BDC_FIELD USING 'ANEP-ANBTR' '0'.
*AVH
clear anep-anbtr.
PERFORM BDC_DYNPRO USING 'SAPMA01B' '0110'.
PERFORM BDC_FIELD USING:
      'BDC_OKCODE' '=UPDA'.
ENDFORM.                    " GENERATE_BDC_DATA_ABAA

I just know that it has an error because the BDC 'mode' is 'E'. And yes, the program used call transaction. So when I run the program and the transaction that is being called shows up, the ok-code pop up window shows up. If you review my code, what i'm trying to do is to change the value of anep-anbtr in screen 285. Thanks a lot guys...

Error: The AcquireConnection method call to the connection manager failed with error code 0xC0202009 using DB2 connection

I have a SSIS project that I am newly running on the SQL server (2005) . It was previously run on my PC. I am importing data from a DB2 server to the SQL server.
I am in the SA group on the server
My connection to DB2 works
When open the package and run it in preview mode, I can retrieve the data.
When I execute the package I get the below errors:
[MIDAS OLE DB Source [1]] Error: The AcquireConnection method call to the connection manager "NGMDSPA.alharris" failed with error code 0xC0202009.
[DTS.Pipeline] Error: component "MIDAS OLE DB Source" (1) failed validation and returned error code 0xC020801C.
What I have already done that has not worked:
The original Protection level was set to EncryptSensitiveWithPassword.
I have reset the Package Password.
I have set the protection level to DontSaveSensitive
I saved the package on the server and set a Package Password.
I created a new package, set the Protection level to DontSaveSensitive, set a package password in a configuration file using the Package Configuration Wizard.
Error continues

Yes. The Drivers are installed and I have a successfull connection. I am trouble shooting the issue on the server in BIDS. I can connect to the DB2 server via the Connectionmanager. I can also preview the data in the OLE
DB source connection. Therefore I know that I have a proper connection
If you're setting option as DontSaveSensitive then you need to pass the connection information from configuration file/ config table. Otherwise it wont be able to use it for connecting to your source/destination servers. This is the recommended way as it
will enable you to change connection info at runtime.
If you want connection info to persist you need to use protection level as EncryptSensitiveUsingUserKey or EncryptSensitiveUsingPassword and set a password.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Error no. 4 in SAPGUI with Graphics call or file transfer

Hi Experts,
I have a requirement that is " I need to display the selected data from database table in bar chart".
I am using the Function Module " GRAPH_MATRIX_3D ".
I am getting the following error message.
" Error no. 4 in SAPGUI with Graphics call or file transfer "
Please can any one help me on this,
It is very urgent I need to deliver this to client very soon.
Please.....
Thanks
Basu

Hi,
have a look at the pdf that comes with the download package. It describes how to structure your data (depending on the chart type).
Use the Chart Designer to create your customizing settings (chart type, colors etc) and save them as a customizing XML file.
Finally have a look at report GRAPHICS_IGS* that shows how to use the XML in your own report and send them to the IGS (by using the class CL_IGS_CHART_ENGINE).
Regards, Kai

I just received my i phone 4,inserted Amayim with 4G plan,but showing noservice and bar with emergency calls only screen.Also when i down loaded i tunes to my laptop (windows7) there is an error(9808) message saying i tunes store not supported completely.

i just received my i phone 4,inserted Amayim with 4G plan,but showing noservice and bar with emergency calls only screen.Also when i down loaded i tunes to my laptop (windows7) there is an error(9808) message saying i tunes store not supported completely.

first of all the iphone 4 is not a 4G phone
second it sounds like your iphone could be locked to another operator then the sim you have inserted

Error in BDC Call transaction

Hi,
I am uplaoding CoA profile data using BDC call transaction method, but records could not be uplaoded because of the error " Screen 0000 is too large for internal batch input Area". I didnt understand what is the reason for this error.
Could you plesae help in this?

Hi,
Keep the REFRESH KTAB after first Endloop.
Like
LOOP AT ITAB.
     LOOP AT KTAB.
    ENDLOOP.
    REFRESH KTAB.
ENDLOOP.
Edited by: subas Bose on Mar 26, 2010 7:17 PM

Error in bdc call xsaction

actually i wnt 2 rectify dat error which i got in format_message thru error msg....in bdc call transaction so do i hv 2 write some extra code like gui_download something.....or change flat file......plz tell me the code if u know or tell me solution in wt way to correct it

Hi
Use BDC MEssage structure in Call transaction syntax and capture the message...
U r not define BDC message in ur call transaction Statement.
Regards:
Prabu

Error hanlind with BDC Call Transation

Similar Messages

Maybe you are looking for