Call transaction syntax

hi expert,
I have called a program using submit from my program.
and i passed some value through it.
for example
SUBMIT ZRME222
        WITH PRINTER# = ztca001-zz_gchr2
        WITH P_QTYLBL = v_lifmg
        WITH S_KUNNR  = v_kunnr
        WITH S_MATNR  = i_zvsd006-matnr
        and return.
but in place of this i have to use a call transcation to call this program.
my problem is how to pass the screen variable through CALL TRANSATION ,  I have not to create any BDC for this.
Is there any syntax which can perform this task.
thanks in advance.

Well, first if this program is a REPORT program, you should always call it using the SUBMIT statement rather than a CALL TRANSACTION.  If your program is a module pool program, then you should use CALL TRANSACTION instead of SUBMIT.  In the case where you have no control over the CALLED program, meaning you can't change it, then you would need to do a BDC to pass the values to this transaction. If you do have control over this program you could use memory to pass the values, for example, in the calling program, use the EXPORT statement to pass the values to memory, and in the called program, use IMPORT to get the values.  And of course, this is just one approach.
Regards,
Rich Heilman

Similar Messages

  • Problem with CALL Transaction syntax

    Hi All,
    I have created  a report in which Im displaying Sales order, planned order n production order details.
    In the output if the user double clicks, anyone of the sales order/planned order/production order no, it has to take to concern transaction.
    Sales order and planned order are perfectly working.
    problem is with production order, it is not displaying, the exact order no.
    my code:
    WHEN '&IC1'.
          IF rs_selfield-fieldname = 'VBELN'.
         READ TABLE gt_final_so INTO wa_final_so INDEX rs_selfield-tabindex
            SET PARAMETER ID 'AUN' FIELD wa_final_so-vbeln.
            CALL TRANSACTION 'VA03' AND SKIP FIRST SCREEN.
          ELSEIF rs_selfield-fieldname = 'PLNUM'.
         READ TABLE gt_final_so INTO wa_final_so INDEX rs_selfield-tabindex.
            SET PARAMETER ID 'PAF' FIELD wa_final_so-plnum.
            CALL TRANSACTION 'MD13' AND SKIP FIRST SCREEN.
          ELSEIF rs_selfield-fieldname = 'AUFNR'.
         READ TABLE gt_final_so INTO wa_final_so INDEX rs_selfield-tabindex.
            SET PARAMETER ID 'ANR' FIELD wa_final_so-aufnr.
            CALL TRANSACTION 'COR3' AND SKIP FIRST SCREEN.
    In debugging I checked, after call transaction, the system executing the following code, here CAUFVD-AUFNR is initial.
    So, it has been picking some different no.
          Starten Batchrezept über Einsatzplanung - DO-THANH
      MODULE GET_PARAMETER OUTPUT.
        IF CAUFVD-AUFNR IS INITIAL.
          GET PARAMETER ID 'BR1' FIELD *CAUFVD-AUFNR.
          IF NOT *CAUFVD-AUFNR IS INITIAL.
            CAUFVD-AUFNR = *CAUFVD-AUFNR.
          ENDIF.
        ENDIF.
      ENDMODULE.                             " GET_PARAMETER  OUTPUT
    Pls help me how to resolve the above problem.
    Valuable suggesstion will be highly appreciated.
    regards,
    Priya

    Hi,
    Note that the code as different Parameter id
    you are setting the parameter 'ANR'
    SET PARAMETER ID 'ANR' FIELD wa_final_so-aufnr.
    Where as in that method it is reading the parameter id 'BR1'
    GET PARAMETER ID 'BR1' FIELD *CAUFVD-AUFNR.
    so try by setting  the 'BR1' in set parameter.
      ELSEIF rs_selfield-fieldname = 'AUFNR'.
         READ TABLE gt_final_so INTO wa_final_so INDEX rs_selfield-tabindex.
            SET PARAMETER ID 'BR1' FIELD wa_final_so-aufnr.
            CALL TRANSACTION 'COR3' AND SKIP FIRST SCREEN.
    Regards,
    Kiruba.

  • Track error records in Call Transaction method

    Hi
    I have used call transaction method for uploading legacy data.
    I need to track the error record.
    Please help me to find out the solution.
    Thanks in advance
    Reagards
    shriraam

    HI,
    !. Obtain  the  messaged into an Interal table of type BDCMSGCOLL using Call Transaction  syntax..
                   Call Transactio <Tcode>
                           using <BDC Table>
                          mode  <A/N/P>
                          update  <A/S>
                         messages  INTO <mSGTAB>
    2. Read the Msg table for eroors and success messages
    3. Then format the messge with the help of Function Module  :'Format_messages'.
    4. Display the respective messges with the help of write statements or with the help of ALV.
    Rgds
    Umakanth

  • Call transaction passing values

    Hi Experts,
          I have a report program from which i need to call a transaction to insert a record.Brief description of the problem is as follows:
          User enters some value of  Ware house No,Inventory record and Count in a transaction say 'T1'.
    The entries are then checked in the database table.If no record exist then some other transaction 'T2'  is called passing these values of Ware house No,Inventory record No and Count.Please suggest a way how to pass multipe values from 1 transaction to other.
                            Help will be appreciated.
    Regards
    Sourabh

    Hi,
    call transaction syntax is ""call transaction <transaction code>using<BDCtab>mode<A/N/E>update<S/A>message into <internal table>
    <b>
    CALL TRANSACTION tcod [AND SKIP FIRST SCREEN] [USING itab].</b>
    The <b>USING ITAB</b> addition in the <b>CALL TRANSACTION </b>statement allows you to pass an internal table itab to the new transaction. itab has the format of a batch input table.
    Feel free to revert back.
    --Ragu
    Message was edited by:
            Raguraman C

  • Session method and call transaction methos which one is the sap recomonded

    hi
    PLease give me the answer to these questions.
    session method and call transaction methos which one is the sap recomonded why .
    2) if we want to maintain BDC program in all the systems.wt to d0

    Hi Revethi,
    Here is the difference between the Session and Call Transaction method.
         Session
    Session method supports both small amount of data aswell as large amount of data
    2) data processing is asynchronus and data updation is synchronus.
    3) it process multiple apllication while perfomaning validations.
    4) in session method data will be updated in data base only after processing session only.
    5) system provide by default logfile for handling error records.
    6) it supports both foreground aswell as background process
    in bdc we use FM ... bdc_open_group " for creating Session
    bdc_insert " adding transaction and bdcdata table for updating database
    bdc_close_group " for closing Session
          Call Transaction
    Call transaction exclusively for small amout of data
    2) it supports only one apllication while perfoming validations
    3) there is no default logfile, We can explicitly provide logic for creating logfile for handling error records.
    we can create logfile by using structure....BDCMSGCOLL
    4) it doesn't support background processing.
    5) data processing is synchronous and Data updation is Synchronous( default), in
    this method also supports daya updation in asynchronus process also.
    Syntax:
    Call transaction <transaction-name> using BDCDATA
    mode <A/N/E> update <L/A/S>
    messages into BDCMSGCOLL.

  • What are the parameters in Call transaction method?

    Hi ABAPER'S,
        Please give me what are the parameters in call transaction method?
    Thanks,
    Prakash

    Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
    Syntax:
    CALL TRANSACTION <tcode>
    USING <bdc_tab>
    MODE  <mode>
    UPDATE  <update>
    <tcode> : Transaction code
    <bdc_tab> : Internal table of structure BDCDATA.
    <mode> : Display mode:
    A
    Display all
    E
    Display errors only
    N
    No display
    <update> : Update mode:
    S
    Synchronous
    A
    Asynchronous
    L
    Local update
    A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
    Prepare a BDCDATA structure for the transaction that you wish to run.
    With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
    CALL TRANSACTION 'TFCA' USING BDCDATA
    MODE 'A'
    UPDATE 'S'.
    MESSAGES INTO MESSTAB.
    IF SY-SUBRC <> 0.
    <Error_handling>.
    ENDIF.
    The MODE Parameter
    You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
    A Display all. All screens and the data that goes in them appear when you run your program.
    N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
    E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
    The display modes are the same as those that are available for processing batch input sessions.
    The UPDATE Parameter
    You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
    A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
    Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
    If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
    S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
    L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
    The MESSAGES Parameter
    The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
    You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
    (This example uses a flight connection that does not exist to trigger an error in the transaction.)
    DATA: BEGIN OF BDCDATA OCCURS 100.
    INCLUDE STRUCTURE BDCDATA.
    DATA: END OF BDCDATA.
    DATA: BEGIN OF MESSTAB OCCURS 10.
    INCLUDE STRUCTURE BDCMSGCOLL.
    DATA: END OF MESSTAB.
    BDCDATA-PROGRAM = 'SAPMTFCA'.
    BDCDATA-DYNPRO = '0100'.
    BDCDATA-DYNBEGIN = 'X'.
    APPEND BDCDATA.
    CLEAR BDCDATA.
    BDCDATA-FNAM = 'SFLIGHT-CARRID'.
    BDCDATA-FVAL = 'XX'.
    APPEND BDCDATA.
    BDCDATA-FNAM = 'SFLIGHT-CONNID'.
    BDCDATA-FVAL = '0400'.
    APPEND BDCDATA.
    CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
    MESSAGES INTO MESSTAB.
    LOOP AT MESSTAB.
    WRITE: / MESSTAB-TCODE,
    MESSTAB-DYNAME,
    MESSTAB-DYNUMB,
    MESSTAB-MSGTYP,
    MESSTAB-MSGSPRA,
    MESSTAB-MSGID,
    MESSTAB-MSGNR.
    ENDLOOP.
    The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
    Return codes:
    Value
    Explanation
    0
    Successful
    <=1000
    Error in dialog program
    > 1000
    Batch input error
    System fields:
    Name:
    Explanation:
    SY-MSGID
    Message-ID
    SY-MSGTY
    Message type (E,I,W,S,A,X)
    SY-MSGNO
    Message number
    SY-MSGV1
    Message variable 1
    SY-MSGV2
    Message variable 2
    SY-MSGV3
    Message variable 3
    SY-MSGV4
    Message variable 4
    Error Analysis and Restart Capability
    Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
    You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
    write out or save the message table
    use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

  • BDC call transaction

    Hi All,
      Help needed. Im facing a problem in BDC call transaction. Im calling a z screen ie i have developed a modulepool prog. In this I have given a zscreen.
    Now by using a call transasction method im calling this screen ie the zscreen and i  want to update a z table through a flat file.
    the system is able to read the flat file and then im able to read it in my internal table. after this im transfering this internal table content in the BDCtable it is even taking it up but then when im calling the command:
    CALL TRANSACTION 'YVTRANS' USING jtab MODE 'A' UPDATE 'S' MESSAGES INTO ktab.
    It takes me to the screen connected by the ztcode yvtrans. but no data is coming in the screen . and then vn im inserting the content but nothing happens wat could be the probable error.
    This is my code:
    *& Report  ZBDCCALLTXN1
    REPORT  zbdccalltxn1.
    *& Report  ZBDCCALLTXN
    *REPORT  zbdccalltxn.
    PREDEFINED TABLES ***
    TABLES:zemp.
    INTERNAL TABLE TO UPLOAD FLAT FILE ***
    DATA:BEGIN OF itab OCCURS 0,
         empno LIKE zemp-empno,
         name LIKE zemp-empname,
         deptno LIKE zemp-deptid,
         deptname LIKE zemp-deptname,
         END OF itab.
    INTERNAL TABLE FOR MAPPING USING BDCDATA ***
    DATA:BEGIN OF jtab OCCURS 0.
            INCLUDE STRUCTURE bdcdata.
    DATA:END OF jtab.
    INTERNAL TABLE FOR ERROR CAPTURING USING BDCMSGCOLL ***
    DATA:BEGIN OF ktab OCCURS 0.
            INCLUDE STRUCTURE bdcmsgcoll.
    DATA:END OF ktab.
    FUNCTION MODULE TO UPLAOD FLAT FILE ***
    CALL FUNCTION 'UPLOAD'
      EXPORTING
        filename                      = 'C:\Documents and Settings\mad13363\Desktop\file.txt'
       filetype                      = 'ASC'
                       HAS_FIELD_SEPARATOR           = ' '
                       HEADER_LENGTH                 = 0
                       READ_BY_LINE                  = 'X'
                       DAT_MODE                      = ' '
                       CODEPAGE                      = ' '
                       IGNORE_CERR                   = ABAP_TRUE
                       REPLACEMENT                   = '#'
                       CHECK_BOM                     = ' '
                       VIRUS_SCAN_PROFILE            =
                     IMPORTING
                       FILELENGTH                    =
                       HEADER                        =
      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
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    READ DATA FROM ITAB ***
    LOOP AT itab.
      REFRESH jtab.
      PERFORM sub USING 'YVTRANS' '0100'.
    TRANSFER THE DATA FROM INTERNAL TABLE TO APLLICATION ***
      PERFORM sub1.
    TO SAVE THE RECORDS IN DB SERVER ***
    PERFORM sub1 USING 'BDC_OKCODE' 'INSERT'.
    LOGIC TO PROVIDE VALIDATIONS USING BDCDATA, DISPLAY MODE, BDCMSGCOLL ***
      CALL TRANSACTION 'YVTRANS' USING jtab MODE 'A' UPDATE 'S' MESSAGES INTO ktab.
    LOGIC REQUIRED FOR LOG FILE ***
      LOOP AT ktab.
        IF ktab-msgtyp = 'I' OR
            ktab-msgnr = 000.
          WRITE:/1 'VENDOR', 15 itab-empno, 30 'INSERTED'.
        ELSEIF ktab-msgtyp = 'E' OR
                  ktab-msgnr = '001'.
          WRITE:/1 'VENDOR', 15 itab-empno, 30 'NOT INSERTED'.
        ENDIF.
      ENDLOOP.
      REFRESH ktab.
    ENDLOOP.
    FROM TO PASS  PRG NAME, SCREEN NUMBER AND FIRST SCREEN ***
    FORM sub USING a b.
      CLEAR jtab.          " CLEAR REFRESHES WORK AREA
      jtab-program = a.
      jtab-dynpro = b.
      jtab-dynbegin = 'X'.
      APPEND jtab.
    ENDFORM.                    "SUB
    FROM TO PASS FEILD NAME AND FIELD VALUE ***
    FORM sub1.
      CLEAR jtab.
      jtab-fnam = 'zemp-EMPNO'.
      jtab-fval = itab-empno.
      jtab-program = 'YVTRANS'.
      jtab-dynpro = '0100'.
      APPEND jtab.CLEAR jtab.
    *Passing screen information to BDCDATA
      jtab-fnam = 'ZEMP-EMPNAME'.
      jtab-fval = itab-name.
      jtab-program = 'YVTRANS'.
      jtab-dynpro = '0100'.
      APPEND jtab.CLEAR jtab.
      jtab-fnam = 'ZEMP-DEPTID'.
      jtab-fval = itab-deptno.
      jtab-program = 'YVTRANS'.
      jtab-dynpro = '0100'.
      APPEND jtab.CLEAR jtab.
      jtab-fnam = 'ZEMP-DEPTNAME'.
      jtab-fval = itab-deptname.
      jtab-program = 'YVTRANS'.
      jtab-dynpro = '0100'.
      APPEND jtab.CLEAR jtab.
    *Passing BDC_OKCODE to BDCDATA
      jtab-fnam = 'BDC_OKCODE'.
      jtab-fval = 'INSERT'.
      APPEND jtab.CLEAR jtab.
    ENDFORM.                                                    "sub1
    reward for all useful ans

    Hi madhvi,
                       You are using jtab within the form.. i dont think you can use it directly inside ur FORM sub1 without declaring it or without passing it. and it will give you the syntax error.
    and please send me the step by step code you have written in editor so that i can check it and can reply you with proper solution'
    Thanks ,
    Prasanna

  • Call Transaction In MV50AFZ1 ?

    Hi Everyone,
    I have a senario , where in based on user inputs before posting goods issue in delivery processing (vl02n),
    I need to call a Z-Transaction and update some details in it.
    Now for that i created an include for the enhancement MV50AFZ1 and tried to write Call transaction statement as follows:
    call TRANSACTION zwb01.
    which throws the following syntax error: "Field ZWB01 is unknown.it is neither in one of the specified tables nor defined by a data statement"
    Anyone has any idea on this, can i call transaction in an exit,if yes wat is it that i am missing out here??
    Thanks,
    sachin

    >
    Sachin Soni wrote:
    > even if this transaction updates some z-tables and then returns?
    exactly, in fact this is the problem itself. It will update the transaction from which it was called as well - but that transaction is only "half-ready" and this will lead to inconsistent database entries.

  • CALL TRANSACTION in user dialog

    Hi!
    I'm having problem to use syntax CALL TRANSACTION in user dialog (SE80).  My syntax is as follows:
    CALL TRANSACTION 'F-43' USING BDCDATA MODE 'N' UPDATE 'S'
              MESSAGES INTO t_msg.
    My problem is I cannot execute this syntax in background mode although I set the MODE as N(Do not display) or P(Do not display; debugging possible).
    However, if I set MODE as A(Display screen) or E(Display only if an error occurs), it works but foreground execution.
    Hope to get respond from you guys.
    Thank you and best regards.

    Hi,
    Chk this link if it can help you.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_aba/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d3732353531%7d
    Regards,
    Balaji
    *Rewrds for helpful answers

  • Call Transaction in Background for IW52

    Hi All..
    When i execute my BDC (Call Transaction) in foreground, the code will update IW52 screens without any errors/warnings.
    But if we schedule this in background, the IW52 screens are not getting updated.
    Even there are no Errors observed.
    We have used the syntax as follows..
    CALL Transaction IW52 using it_bdcdata MODE 'N' messages into it_bdcmsg.
    Can anyone help me how to rectify it and make it to execute successfully in background mode..??
    Your Help will be highly appreciated..
    Regards
    Pavan

    Hello Friends...
    I am running a call Transaction code in Background mode.
    I am facing Error message..
    If i run the same in foreground, it is working fine...
    Error Message is "No Batch Input data for screen <SAPNV screen No>"
    Expecting your guidence in this case...
    Regards
    Pavan
    Message was edited by:
            Pavan Sanganal

  • Calling FI Validation Rules in BPM server through call transaction

    I m trying to call FI validation rules through call transaction (for FBV0) in BPM server but in the messages table of call transaction it does not gives us the validation rules error messages while when i run manually the transaction in R/3 system i get the validation error messages. So please tell how i can get these validation error messages when called through BPM server.

    Hi madhvi,
                       You are using jtab within the form.. i dont think you can use it directly inside ur FORM sub1 without declaring it or without passing it. and it will give you the syntax error.
    and please send me the step by step code you have written in editor so that i can check it and can reply you with proper solution'
    Thanks ,
    Prasanna

  • Can anybody pls tell me  limitations of BDC Session & Call transaction?

    hi, Guys, this is srinivas.
    How can we deside which method is to(BDC session/ Call transaction)
    use to upload data to SAP database?
    Can we run Call Transaction in Background?
    Which is preferable for bulk data? and Why?
    how can we restart Session if any error occurs?
    Thanku?

    Hi,
    Hope it helps this......
    SAP BDC INTERVIEW QUESTIONS  & ANSWERS
    1.       What is full form of BDC Session?
    Batch Data Communication Session.
    2.       What are the steps in a BDC session?
    The first step in a BDC session is to identify the screens of the transaction that the program will process.  Next step is to write a program to build the BDC table that will be used to submit the data to SAP.  The final step is to submit the BDC table to the system in the batch mode or as a single transaction by the CALL TRANSACTION command.
    3.       How do you find the information on the current screen?
    The information on the current screen can be found by SYSTEM à STATUS command from any menu.
    4.       How do you save data in BDC tables?
    The data in BDC tables is saved by using the field name ‘BDC_OKCODE’ and field value of ‘/11’.
    5.       What is the last entry in all BDC tables?
    In all BDC tables the last entry is to save the data by using the field name BDC_OKCODE and a field value of ‘/11’.
    6.       What is a multiple line field?
    A multiple line field is a special kind of field which allows the user to enter multiple lines of data into it.
    7.       How do you populate data into a multiple line field?
    To populate data into a multiple line field, an index is added to the field name to indicate which line is to be populated by the BDC session (Line index).
    8.       Write the BDC table structure.
    BDC table structure
    FIELD                     TYPE                            DESCRIPTION
    Program                CHAR (8)                      Program name of transaction.
    DynPro                 CHAR (4)                      Screen number of transaction.
    DynBegin              CHAR (1)                      Indicator for new screen.
    Fnam                    CHAR (35)                     Name of database field from screen.
    Fval                      CHAR (80)                     Value to submit to field.
    9.       Does the CALL TRANSACTION method allow multiple transactions to be processed by SAP?
    No.  The CALL TRANSACTION method allows only a single transaction to be processed by SAP.
    10.    Does the BDC-INSERT function allow multiple transactions to be processed by SAP?
    Yes.
    11.    What is the syntax for ‘CALL TRANSACTION’?
    CALL TRANSACTION trans .
    Three possible entries are there for MODE.
                      A          -           Show all screens.
                      E          -           Show only screens with errors.
                      N          -           Show no screens.
    Regards,
    V.Balaji
    Reward if usefull

  • Calling Transaction code & returning back to calling program

    Hi,
    I have requirement as below
    Write the report to call the transaction code say for example different tcode (1000 in number) need to be executed and after every tcode execution it should return back to calling report. I tried using "CALL TRANSACTION 'ABC' AND SKIP FIRST SCREEN"  it does execute the tcode but need the user interaction to return back to report, where here i want do this programatically.
    can someone please help me & what is possible ways this can be do able.
    Thanks,
    John.

    There are two method of BDC
    1- Call transaction method
    2- BDC Session method
    In this case you can use call tansaction method.
    Syntax- call tansaction abc using gt_bdcdata.
    Do the recording with t-code SHDB for that particular transaction and after the necessary modification use it in your program.
    Please check f1 help of call transaction for details.

  • Idoc syntx error me21 , abap proxy call transaction

    Hi Experts,
    I am struck with the below problem, could you please shed some light on the issue, appreciate your help and  rewarded.
    scenario:
    XI sends NEW PO message to abap proxy, in abap proxy we populate bdc_tab
    and call ME21 as below
    CALL TRANSACTION  'ME21' using bdc_tab mode 'N' update 'S'  messages into messtab.
    problem:
    EKSEKS01 idoc is getting created with syntax error status code :26  in ECC5.0
    only 5 sigments are generated in the idocs. the three segments ( E1PISHO, E1PISIO,E1PISSO not generated).
    after transaction executed it returns subrc 1001, msgid--> ME, MSGNO --> 218.
    Thanks In Advance.
    Ranjit.

    Hi Atish and Nishant,
    Thanks much  for the immediate response.
    1.Would like to know what is the mandatory data to be passed for PO creation in BDC table.
    2. Is there any user exit or where the idoc creation happens during me21 execution.
    I have verified the po in we02 , as before mentioned the three sigments are not getting created and i am not sure the reason.
    Note: We didnot have any output configured in ECC 5.0 for this idoc to be created.
    I am really not able to locate in debug mode FOR  ME21, where this ekseks01 idoc getting created and triggered.
    Appreciate your help.
    Thanks in Advance.
    Ranjit.

  • Call Transaction and session

    How to decide between call transaction and session methods.which one to use for data transfer?
    and how to schedule session method in background mode?
    Moderator message - Please search before asking - post locked
    Edited by: Rob Burbank on Nov 23, 2009 9:38 AM

    Hi Kiranmayi,
    1. It depends on various factors
           a. As per the requirement mentioned in TDD
           b. If user/Clnt needs the Error Log to be displayed in specific format.
              since, In u2018Call Transactionu2019, the transactions are triggered at the time of processing itself and so the ABAP
              program must do  the error handling.
           c. We can update the database both synchronously and asynchronously. We can specify the mode in the program.
              Faster than session method if uses Asynchronous update.   
    2.  Whenever there is large no of records need to be processed and user interaction is not required then you canschdule the
         program to run in Background.
        In session method you can submit the session in background job using 'RSBDCSUB'.
    syntax:
      SUBMIT (SUBREPORT) 
       USER SY-UNAME 
       VIA JOB JNAME 
       NUMBER JNUMB 
       WITH QUEUE_ID EQ QID 
       WITH MAPPE EQ GROUPID 
       WITH MODUS EQ 'N' 
       WITH LOGALL EQ LMODUS 
    AND RETURN. 
    Note: You can refer the sdn site for further more details

Maybe you are looking for