Call Transaction BDC for ME9F in Background

Hi All,
I am posting data to ME9F transaction by using CALL TRANSACTION Method. This runs good in foreground but when i try to run this in the background its not posting the data.Could you please let me know any solution how we can resolve this issue. Thanks in advance.
Regards,
Suresh

According to OSS note #708037:
When transaction ME9F is called in a program with a batch input file, the messages are output to the spool even when they had to be deleted according to the batch input information. This occurs only when the program is called in the background.

Similar Messages

Writing a Batch Input or Call Transaction program for transaction code MMAM

Hi All,
I'm writing a Batch Input or Call Transaction program for transaction code MMAM (Changing Material Type). The program was able to run but somehow I was not able to capture the log of the output after running MMAM. The log was not part of the SY-MESSAGE so adding in MESSTAB into call transaction doesn't help while BDC session logs shows only the transaction was processed.
Anyone has encounter such problems before?
Regards,
Ramu.

Hi
Overview of Batch Input Session
The first batch input method is to create a batch input session. It is the processing of this batch input session that updates the database, not the execution of the batch input program. i am giving you example for Change Vendor you practice for ur tcode
For our example, we will use the Change Vendor transaction (FK02) to add a street address to an already existing vendor.
Step #1
Use SystemStatus menu path to determine online program name (SAPMF02K), screen number (0110)
Step #2
Use F1 key and Technical Info pushbutton in each screen field to be filled to determine the field name.
Step #3
Determine how to proceed in the transaction
(save the record by clicking on the Save pushbutton or pressing the F11 key).
The process flow of CALL TRANSACTION
A program that uses CALL TRANSACTION USING to process legacy data should execute thefollowing steps:
Prepare a BDCDATA structure for the transaction that you wish to run.
Prepare a internal table to store error messages Tab_Mess like structure of BDCMSGCOLL.
With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
CALL TRANSACTION MM01' USING BDCDATA MODE 'A' UPDATE 'S'. MESSAGES INTO TAB_MESS.
IF SY-SUBRC <> 0.
<Error_handling>.
ENDIF.
Overview of Batch Input Session
The first batch input method is to create a batch input session. It is the processing of this batch input session that updates the database, not the execution of the batch input program

Can we record two transactions and use for a Call-transaction BDC?

can we record two transactions and upload data using Call-transaction method in BDC ?IF not why?

Hi Prakash,
Here i used two transactions.
REPORT zra_gl_cr NO STANDARD PAGE HEADING LINE-SIZE 255.
TYPE-POOLS: truxs.
DATA: it_raw TYPE truxs_t_text_data.
DATA:messtab1 LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
DATA:messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
DATA: bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF i_mess OCCURS 0,
l_mstring(480),
msgnr(5),
msgv1(15),
END OF i_mess.
DATA:i_mess1 LIKE i_mess OCCURS 0 WITH HEADER LINE.
DATA: l_mstring(480),l_mstring1(480).
DATA: BEGIN OF it_itab OCCURS 0,
      saknr(10),    "G/L a/c number.
      bukrs(4),     "Company Code.
      ktoks(4),     "G/L a/c group.
      xplacct(1),   "P&L statement account.
      xbilk(1),     "Balance sheet account.
      txt20_ml(20), "G/L a/c short text.
      txt50_ml(50), "G/L a/c long text.
      waers(5),     "Account currency.
      MWSKZ(2),
      mitkz(1),     "Reconciliation a/c for a/c type.
      xopvw(1),     "Open item management
      xkres(1),     "Line item display.
      zuawa(3),     "Sort Key.
      fstag(4),     "Field status group.
      xintb(1),     "Post automatically only.
      hbkid(5),     "House bank.
      hktid(5),     "Account id.
      vzskz(2),     "Interest indicator
      END OF it_itab.
DATA: hdate LIKE sy-datum.
                      Selection Screen                       *****
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(15) text-103. " FOR FIELD P_FILE1.
SELECTION-SCREEN POSITION 25.
PARAMETERS : p_file1 LIKE rlgrap-filename.
SELECTION-SCREEN END OF LINE.
                      Initialization                         *****
INITIALIZATION.
                   At Selection Screen                       *****
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
Perform file_selection will help to select the location of the file
PERFORM file_selection.
                   Start-Of-Selection                        *****
START-OF-SELECTION.
Perform data_upload will help to upload the data from the flat file
to the internal table.
PERFORM data_upload.
PERFORM open_group.
   Peform bdc_upload will help to upload the data from the internal
   table into its respective fields.
PERFORM bdc_fspo.
PERFORM bdc_upload.
PERFORM exp_log.
PERFORM close_group.
   Perform display_log will prepare a log for the data that has been
   uploaded
   PERFORM display_log.
                    End-Of-Selection                           ****
END-OF-SELECTION.
*&      Form file_selection
      To select the location of the file
FORM file_selection .
CALL FUNCTION 'WS_FILENAME_GET'
    EXPORTING
      def_filename     = ' '
      def_path         = 'C:\'
      mask             = ',.txt,.xls.'
      mode             = 'O'
      title            = 'Open a excel file'
    IMPORTING
      filename         = p_file1
    EXCEPTIONS
      inv_winsys       = 1
      no_batch         = 2
      selection_cancel = 3
      selection_error = 4
      OTHERS           = 5.
ENDFORM.                    " file_selection
*&      Form data_upload
     To upload the data from the file location to the internal table.
FORM data_upload .
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
    EXPORTING
    I_FIELD_SEPERATOR        =
      i_line_header            = 'X'
      i_tab_raw_data           = it_raw
      i_filename               = p_file1
    TABLES
      i_tab_converted_data     = it_itab
   EXCEPTIONS
      conversion_failed        = 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.                    " data_upload
*&      Form bdc_upload
To upload the data from the internal table into its respective fields.
FORM bdc_upload .
LOOP AT it_itab.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ACC_CRE'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_KEY-SAKNR'.
perform bdc_field       using 'GLACCOUNT_SCREEN_KEY-SAKNR'
                              it_itab-SAKNR.
perform bdc_field       using 'GLACCOUNT_SCREEN_KEY-BUKRS'
                              it_itab-BUKRS.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=2102_GROUP'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_COA-KTOKS'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                              it_itab-KTOKS.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XPLACCT'
                              it_itab-XPLACCT.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=2102_BS_PL'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_COA-XBILK'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                              it_itab-KTOKS.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XPLACCT'
                             it_itab-XPLACCT.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XBILK'
                              it_itab-XBILK.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTER'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                              it_itab-KTOKS.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XBILK'
                              it_itab-XBILK.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                              it_itab-TXT20_ML.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                             it_itab-TXT50_ML.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_COA-BILKT'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-BILKT'
                              it_itab-saknr.
    PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=TAB02'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-KTOKS'.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                   it_itab-ktoks.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                                   it_itab-txt20_ml.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                                   it_itab-txt50_ml.
    perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_COA-BILKT'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-BILKT'
                              it_itab-saknr.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=TAB02'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_COA-KTOKS'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                                 it_itab-KTOKS.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_COA-KTOKS'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                              it_itab-KTOKS.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XBILK'
                             it_itab-XBILK.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                              it_itab-TXT20_ML.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                              it_itab-TXT50_ML.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-BILKT'
                             it_itab-saknr.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTER'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-WAERS'
                              it_itab-waers.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                              it_itab-MWSKZ.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                              it_itab-mitkz.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-XOPVW'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                              it_itab-XOPVW.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XKRES'
                              it_itab-XKRES.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                             it_itab-ZUAWA.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                   it_itab-xplacct.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                                   it_itab-xbilk.
       IF it_itab-xbilk = 'X'.
   PERFORM bdc_dynpro USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
   PERFORM bdc_field       USING 'BDC_OKCODE'
                                 '=TAB03'.
   PERFORM bdc_field       USING 'BDC_CURSOR'
                                 'GLACCOUNT_SCREEN_CCODE-WAERS'.
   PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
                                  it_itab-waers.
     PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                              it_itab-xopvw.
     PERFORM bdc_field USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                              it_itab-mitkz.
   ENDIF.
   PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
                                  it_itab-xkres.
   PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                                  it_itab-zuawa.
   PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
   PERFORM bdc_field       USING 'BDC_OKCODE'
                                 '=SAVE'.
   PERFORM bdc_field       USING 'BDC_CURSOR'
                                 'GLACCOUNT_SCREEN_CCODE-FSTAG'.
   PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                                  it_itab-fstag.
   PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
                                  it_itab-xintb.
   PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-HBKID'
                                  it_itab-hbkid.
   PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-HKTID'
                                  it_itab-hktid.
   PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_CCODE-VZSKZ'
                                  it_itab-vzskz.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=TAB03'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-WAERS'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-WAERS'
                              it_itab-WAERS.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                              it_itab-MWSKZ.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                              it_itab-MITKZ.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                             it_itab-ZUAWA.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTER'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-FSTAG'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                             it_itab-FSTAG.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SAVE'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-FSTAG'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                              it_itab-FSTAG.
   PERFORM bdc_transaction USING 'FS00'.
    CALL TRANSACTION 'FS00' USING bdcdata MODE 'A'
                                          UPDATE 'S'
                                         MESSAGES INTO messtab1.
    PERFORM mess1.
    REFRESH bdcdata[].
ENDLOOP.
ENDFORM.                    " bdc_upload
*&      Form bdc_fspo
      text
FORM bdc_fspo .
LOOP AT it_itab.
    PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ACC_CRE'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_KEY-SAKNR'.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
                                  it_itab-saknr.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_KEY-KTOPL'
                                  '1000'.
    PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=2102_GROUP'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-KTOKS'.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                  it_itab-ktoks.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                   it_itab-xplacct.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                                  it_itab-xbilk.
    PERFORM bdc_dynpro      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=SAVE'.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                   it_itab-ktoks.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                   it_itab-xplacct.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'GLACCOUNT_SCREEN_COA-TXT50_ML'.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                                   it_itab-txt20_ml.
    PERFORM bdc_field       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                                   it_itab-txt50_ml.
*perform bdc_transaction using 'FSP0'.
    CALL TRANSACTION 'FSP0' USING bdcdata MODE 'A'
                                          UPDATE 'S'
                                         MESSAGES INTO messtab.
    PERFORM mess.
    REFRESH bdcdata[].
ENDLOOP.
ENDFORM.                    " bdc_fspo
*&      Form mess
      text
--> p1        text
<-- p2        text
FORM mess .                                                 "fsp0
LOOP AT messtab.
    CALL FUNCTION 'FORMAT_MESSAGE'
      EXPORTING
        id        = messtab-msgid
        lang      = messtab-msgspra
        no        = messtab-msgnr
        v1        = messtab-msgv1
        v2        = messtab-msgv2
        v3        = messtab-msgv3
        v4        = messtab-msgv4
      IMPORTING
        msg       = l_mstring
      EXCEPTIONS
        not_found = 1
        OTHERS    = 2.
    CONDENSE l_mstring.
    i_mess1-l_mstring = l_mstring(250).
    i_mess1-msgnr = messtab1-msgnr.
    i_mess1-msgv1 = messtab1-msgv1.
    APPEND i_mess1.
ENDLOOP.
ENDFORM.                    " mess
*&      Form mess1
      text
--> p1        text
<-- p2        text
FORM mess1 .                                                "fs00
LOOP AT messtab1.
    CALL FUNCTION 'FORMAT_MESSAGE'
      EXPORTING
        id        = messtab1-msgid
        lang      = messtab1-msgspra
        no        = messtab1-msgnr
        v1        = messtab1-msgv1
        v2        = messtab1-msgv2
        v3        = messtab1-msgv3
        v4        = messtab1-msgv4
      IMPORTING
        msg       = l_mstring1
      EXCEPTIONS
        not_found = 1
        OTHERS    = 2.
    CONDENSE l_mstring1.
    i_mess-l_mstring = l_mstring1(250).
    i_mess-msgnr = messtab1-msgnr.
    i_mess-msgv1 = messtab1-msgv1.
    APPEND i_mess.
ENDLOOP.
ENDFORM.                                                    " mess1
*&      Form exp_log
      text
--> p1        text
<-- p2        text
FORM exp_log .
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      filename = 'c:\temp\error_fsp0.txt'
      filetype = 'DAT'
    TABLES
      data_tab = i_mess1.
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      filename = 'c:\temp\error_fs00.txt'
      filetype = 'DAT'
    TABLES
      data_tab = i_mess.
ENDFORM.                    " exp_log
*&      Form bdc_dynpro
      text
     -->PROGRAM    text
     -->DYNPRO     text
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.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDFORM.                    "BDC_Field
********Rewards some points.

Call transaction BDC with different user id

Hello,
We have a BDC program for creating Invoice using "CALL TRANSACTION VF01" method. But there are are few user IDs accessing this program who do not have authorisation to VF01. So requirement is to create Invoice with a common user id.
Please help if it is possible to call transaction with different user id. Please also provide you inputs if you can suggest some other way to fulfill this requirement.
Thanks & Regards,
Rohit

Hi Rohit,
if users are not authorized to post invoice, why is it required to surpass the checks?
A Question the business should answer.
It should not be the consultants obligation to find doubtable ways.
Regards
Clemens

Error in call transaction bdc

hello,
i'm prepare a bdc program for F-22, when i record the process through shdb, an error occurs said a field must be filled( but the field is not on the current screen), and when a press enter a popup dialog said i can fill the field in the next screen.
but when i fill my bdcdata in program according the recording, and then use call transaction to do the BDC job, it stops on the error (Note that when recording, i can press enter and modify the error in the next screen).
could someone give a solution ??
thank you !!

and the message after recording is
Number               1
Transaction          F-22
SY-SUBRC             0
Messages
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0300WEZ001                066
FB01                SAPMF05A                                0300EEZ001                073
I F5 573                   Correct the error reported before on the next screen
FB01                SAPMF05A                                0330WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
FB01                SAPMF05A                                0301WEZ001                066
S F5 312                   Document 100001677 was posted in company code 3100

Call Trasaction (BDC for CRMD_ORDER) in webui

Hi Experts,
I know this is not a good option to use a call transaction in webui nad we are gettinCNTL_ERROR for that too.
Our requirement is like , from custom webui report we are wants to call the BDC with some data based on the inputs.
But here we are getting an error for the statement Call Transaction.
Is it possible to use anyway/ or not allowed in webui......
please suggets alternative.......
Thanks,
Aniket

Hi,
You cannot use CALL TRANSACTION in Web UI. If you want to display standard transaction you'd have to use transaction launcher.
Let me know if you need more help.
Regards
Prasenjit

No batch input data for screen occured in Call Transaction method for PA40

Hi,
I creatred an interface to update an employee action data ( Change of position ) PA40 by using Call transaction method.
while executing the interface, I got the below error.
No batch input data for screen MP049100 200
this interface updated the first employee from file, then after it is giving the below error frequently.
No batch input data for screen MP049100 200
regards,
Ashok Reddy Revoori

The infogroup of action Change Position may be having infotype 0491. The infotypes screen sequence is decided based on employee's country grouping and user group. For the employee where you are receiving error, infotype 0491 screen is appearing for which you do not have BDC data.

Call transaction method for MM42

Hi Guis,
I am using MM42 tcode to Maintain the article Sales Orgnisation wise . For this I am using Call transaction method.
Program is working fine in Display mode when I excute it in No display mode for some Sales Org I am getting message that
'SOME OF THE GROUP DATA HAS BEEN BLOCKED BY ABAPER(My id) ' .
I tried using diffrent recording ways but the problem is not solving .
Will you please any body solve my problem .
Thanks,
Santhosh.V

HI,
Check in SM12 and see fi there are any locks with ur id.close all the internal sessions and refresh the lock list..
Now try again and see. Hope your id is not shared
Regards,
Nagaraj

Need BDC code for Call Transaction of VL31N, which creates Inbound del.s,

Hi Experts,
Is any body does have the BDC (CALL TRANSACTION) code for VL31N transaction, where we can crete INBOUND deliveries from Purc Orders.
Actually, currently am doing by using FM - GN_DELIVERY_CREATE, but, its not given me a chance to incorporate BATCH SPLIT functionality. So, decided to go with BDC
1 - Is this VL31N is Okay for BDC, bcoz, some where I red that, since its a ENJOY tx, its NOT recommended?
2 - Is there any other FM, BAPI to create INBOUND deliveries from POs, which can take care of BATCH SPLIT functionality?
3 - BDC code for VL31N tx.
thanq
Edited by: Srinivas on Jul 29, 2008 1:47 PM

1 - Is this VL31N is Okay for BDC, bcoz, some where I red that, since its a ENJOY tx, its NOT recommended?
yes you can do that .
2 - Is there any other FM, BAPI to create INBOUND deliveries from POs, which can take care of BATCH SPLIT functionality?
using BDC we can achieve the Barch split functionality.
3 - BDC code for VL31N tx.
Record using SHDB it will give you.

BDC Call Transaction - Doc.No not getting generated in Message Internal tab

Dear All,
I am using BDC Call Transaction method for uploading data for transaction, Iam able to successfully capture the Error messages, sucess messages and the transaction number is also displayed for the bdc run in Mode A, but in case of scheduling the job in background, the Error messages are displayed but the transaction number is not captured in the message Internal table( BDCMSGCOLL).
Kindly look into the matter and revert back for any further info.
Regards
Naresh

Hi,
Please try using the following kind of code in 'CALL TRANSACTION'
    opt-dismode = 'E'.     " Exclusive mode
    opt-defsize = 'X'.
    opt-updmode = 'S'.
    opt-nobinpt = ' '.
    CALL TRANSACTION transaction_code USING ft OPTIONS FROM opt
                                                                         MESSAGES INTO t_bdcmsgcoll .
Hope this will work.
Thanks,
Leo

Screen no change in BDC call transaction method

Hi experts
Greetings!
I have a BDC created in call transaction method for t-code FB01.
Data passed successfully to the first screen but when it navigates to the second screen I am not able to pass any data.
After debugging I found that the issue was because of the DYNPRO value.
It was 8500 when I created this recording but now the screen number shows 350.
Is is possible that screen nos change because of any support stack or OSS notes implementation.
In run time i tried to change the value to 350 and it works fine..
Thanks
Jay

Hi,
LSMW Direct input method is better for your quiry. Becasuse i wrote BDC for FB01 but not working properly.
So i used LSMW, helped me a lot. Progmra name is RFBIBL00. Or else i will export and send you if you want. It can handle multiple line items upto 950.
Thanks,
Sriram

Reg Vendor master upload using BDC Call Transaction Method

Hi All,
Thanks in advance.
I am uploading vendor master data using bdc call transaction method for XK01. In that i am getting an error message that the fields " smtp_addr" ( for email) and "time_zone" (for time zone) doesnot exist on the screen '0110' ( this is the second screen) . the field timezone will be displayed on the screen only when we go for communications button and select the URL field .
Do anybody have the solution for this problem. if possible can you give me the code for that screen.

Create a recording via SM35 (menu go to=>recording), this will generate automatically the code for filling your bdcdata-table...

Hi all, BDC call transaction METHOD, trapping ERRORS

hi
i have developed BDC (recording via call transaction method) for VB01.
could u please tell me how to display records having errors after running recording or to give index of records having errors.
and is it possible to give transaction code for recording since my bdc is executable program.
plase answer both the questions.
thanx

Here is the flow that Raja is explaining to you.
DATA: v_index LIKE sy-tabix.
LOOP AT itab.
v_index = sy-tabix.
*-- prepare the BDC data
CALL TRANSACTION 'VB01' USING bdcdata
                           MODE 'N'
                          MESSAGES INTO bdcmsgcoll.
READ TABLE bdcmsgcoll WITH KEY msgtyp = 'E'.
IF sy-subrc = 0.
*-- Error occured for the record with index <b>v_index</b>
ELSE.
*-- unless there is a success message with this number,
*   it is not succesfull because 'No data for screen xxx'
*   will not show up as an error message type, but will be
* a success message type
    READ TABLE bdcmsgcoll WITH KEY msgnr = '312'.
    IF sy-subrc = 0.
*-- success
    ELSE.
*-- error with index <b>v_index</b>
    ENDIF.
ENDIF.
ENDLOOP.
As you can see, now you have the index of the record where the error occured. Now this will become complicated if you are combining several records into one transaction call. In that case you need to find how you can know all the records that you just accumulated.
As an example, let us say you have an internal table with external number, customer, material, quantity and at every new external number, you want to create a sales order. Until you get a new external number, you will not do the call transaction because until then it will be items of the same sales order. So in this case, after the call transaction, you will have get all the records that belong to making this sales order by using the external number and then prepare your messages.
I hope this is clear.
Srinivas
Message was edited by: Srinivas Adavi

Call transaction for less than 10,000 records

Hi all
Is call transaction advisable for processing less than 10,000 records.
I want to use call transaction for each record and if it fails, pass it to an opened bdc session for manual processing by functional consultants. At the same time, I have to write a report with successful and errored records. Is my approach the only way? Any other ideas are welcome and appreciated
Thanks
ricky

Its completely safe.
Check the return table for all message type E and then recreate your Error table and pass it to BDC open session and can be executed from SM35 in foreground mode. But what happen if there are more say 100 or 200 error records are there.Its not feasible to go and run each record in Foreground mode.Instead Display the error records in an editable ALV with the error message trap from the CALL Transaction return table and let the consultant correct then on the screen and download it, modify it to suit the upload procedure of your report. Then reprocess the file.
Also, display the audit report based on that table.
Regards,
Amit

OOPS in BDC (Call Transaction )

Hi all ,
    Can anyone tell me how call transactin using OOPS works ? If any example or materials would help me.
Thanks and Regards
Raghav

Create a method of class or object. Inside that method, do 'Call Transaction'. For example see business object BUS2038 (maintenance notification) using transtion SWO1 ( it is O for orange not 0(zero)). Select method 'MaintenanceNotific.Display' and press 'Program button' on application Bar. You will see the following code.
BEGIN_METHOD DISPLAY CHANGING CONTAINER.
SET PARAMETER ID 'IQM' FIELD OBJECT-KEY-NUMBER.
CALL TRANSACTION 'IW23' AND SKIP FIRST SCREEN.
END_METHOD.
I hope it helps.

Call Transaction BDC for ME9F in Background

Similar Messages

Maybe you are looking for