CATT mode in BDC

Hi Experts
I have a doubt.
What is the use of CATT mode in bdc and how it works ...
please revert your concepts regarding that.
Regards
Ashwin

Hi Ashwin,
Please refer these threads,
regarding BDC & CATT
Details on CATT MODE
Update Mode and CATT Mode in BDC
Regards,
Arun VS

Similar Messages

  • Reg. Update and CATT mode in BDC

    Hello friends,
    Whn we create new BDC recording in that recording parameters having update mode and CATT mode. so I want to know abt Update mode (Asynchronous, synchronous and local) and CATT mode in BDC.
    Thanks.
    Marmik

    Hi
    CATTMODE
    CATT mode (controlling a CATT procedure)
    The CATT mode can have the following values:
    ' ' No CATT procedure active
    'N' CATT procedure without single screen control
    'A' CATT procedure with single screen control
    UPDATE upd
    Effect
    The specified update mode upd defines the update type. This can have one of the following values:
    'A' Asynchronous update
    'S' Synchronous update
    If the addition UPDATE is not specified, the processing mode is set to 'A' .
    synchronous update
    In synchronous update, you do not submit an update request using CALL FUNCTION... IN UPDATE TASK. Instead, you use the ABAP statement COMMIT WORK AND WAIT. When the update is finished, control passes back to the program. Synchronous update works in the same way as bundling update requests in a subroutine (PERFORM ON COMMIT). This kind of update is useful when you want to use both asynchronous and synchronous processing without having to program the bundles in two separate ways.
    Asynchronous update
    A typical SAP system installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. If, in a dialog work process, the function modules stored in interim storage through CALL FUNCTION ... IN UPDATE TASK are released for processing by means of the ABAP statement COMMIT WORK, the dialog work process will not wait for the update process to finish. This kind of update is called asynchronous update.

  • Update Mode and CATT Mode in BDC

    Hi Experts,
    when we start the recording then we pass the following steps..
    1.Recording Name
    2. Trasaction Code
    3. Update Mode-------*Local
                                  *Synchronous
                                  *Asynchronous
    4.CATT Mode------*No Catt Mode
                              *CATT without indivisual screen control
    CATT with indivisual screeen control
    so i want to know that What is UpdateMode and CATT Mode (seperate meaning of three Categories)..
    i already searched in this forum,
    Thanks in Advance.......
    Kind Regards
    Yogesh

    Hi
    CATTMODE
    CATT mode (controlling a CATT procedure)
    The CATT mode can have the following values:
    ' ' No CATT procedure active
    'N' CATT procedure without single screen control
    'A' CATT procedure with single screen control
    UPDATE upd
    Effect
    The specified update mode upd defines the update type. This can have one of the following values:
    'A' Asynchronous update
    'S' Synchronous update
    If the addition UPDATE is not specified, the processing mode is set to 'A' .
    synchronous update
    In synchronous update, you do not submit an update request using CALL FUNCTION... IN UPDATE TASK. Instead, you use the ABAP statement COMMIT WORK AND WAIT. When the update is finished, control passes back to the program. Synchronous update works in the same way as bundling update requests in a subroutine (PERFORM ON COMMIT). This kind of update is useful when you want to use both asynchronous and synchronous processing without having to program the bundles in two separate ways.
    Asynchronous update
    A typical SAP system installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. If, in a dialog work process, the function modules stored in interim storage through CALL FUNCTION ... IN UPDATE TASK are released for processing by means of the ABAP statement COMMIT WORK, the dialog work process will not wait for the update process to finish. This kind of update is called asynchronous update.

  • CATT Mode in BDC Recording

    Hi Friends
    What is the Use of CATT MODE in recording parameters of  SHDB Recording .
    Can u pls give some valuable information
    Regards
    Krishnan R.

    Hi Krishnan,
    CATT stands for "Computer Aided Test Tool". When the transaction contains more number of sub-screens or if the transaction is more complex to handle (for example, user defined z-transactions), then we use CATT option as they are reusable tests.

  • Diffrence b/w sync & async mode in bdc.

    hi all,
       wat is the diffrence b/w sync & async mode in bdc? plz explain interview point of view.
    regards
    deepak

    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.
    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
    one simple example : You are creating sales order from file and also you want to update header text of sales order.
    when you want to update sales order header text,you need to use save_text function module ,here you need to pass sales order number.
    when you use call transaction update 'A', data will update transaction level and it goes to the next record,here it will not wait for database .
    when you use call transaction update 'S',data will update transaction level and it will update database then it goes next record.
    if you want to update header text,then you need to use sync update
    database commit -
    comitt work - it will update data in database sucessfully
    roll back - it will not update in database.
    Thanks
    Seshu

  • Back ground mode in BDC

    Hi Experts,
    I am using 1 BDC to upload MDQ and NWC data in mm42.
    This BDC is working fine in foreground mode but it is not updating in background mode.
    Why this is happening and how to resolve it.
    rgds
    Amit

    Hi,
    If you are working through presentation server back ground mode doesnot work(gui_upload)
    if you are working through application server it will run in background mode(open Dataset)
    Hope it may help
    Thanks & Regards
    Ramakrishna Pathi

  • Screen resolution with Mode in BDC

    Hi All,
    In call transaction statement I am using mode as well as options from statement but 1 error is coming that i can't use mode and update with options from statement. But I want to run in background as mode 'N' as well as I want the default screen resolution.
    Please tell me some way to solve this issue.
    Regards,
    Sivaram

    Hi ,
    You need not use mode. You can set the values in OPTIONS itself.
    Eg :
    Declare a structure of type ctu_params.
    Data :gs_params type ctu_params.
         gs_params-dismode  = 'N'.
         gs_params-defsize  = 'X'.
    Call transaction 'MM01' using gt_bdccat
                                         messages into gt_bdcmsg
                                         options from gs_parms.
    Try this .
    Best Regards,
    Hari

  • Computer Aided test tool in processing BDC

    Hi friends,
                   I have some doubts regarding the CATT mode in Processing BDC(SHDB transaction).
    1) What's the use of this CATT mode in BDC Processing?
    2) What is  use of"NO CATT, CATT WITHOUT INDIVIDUAL SCREEN CONTROL, CATT WITH INDIVIDUAL SCREEN CONTROL" these three modes in Processing BDC?
    3) What is the difference between the three modes?

    Hi,
        I have searched in the forum regarding this topic. I'am getting only answers like whats is CATT,and what is it used for. Iam unable to find the exact difference between "CATT WITHOUT INDIVIDUAL SCREEN CONTROL" and " CATT WITH INDIVIDUAL SCREEN CONTROL".

  • Error in BDC using 'N' mode while creating production order

    Hi,
    I am trying to create a production order  ( transaction CO01 ) by using a BDC. I just have to fill the header details, components , assign the component to operation , save and exit. When I am running the BDC in 'A' or 'E' mode, it works fine. The 'E' mode doesnt stop anywhere and successfully creates the production order . But when I change the mode to 'N', it throws an error "No batch input data for the screen SAPLCOKO1 0115". I am using Call transaction in BDC to create the production order. What could be the issue? Can someone throw some light?
    Thanks,
    Suganya

    Hi Suganya,
    I guess that Chandra Madapati is right. I also faced the same issue for another transaction.
    If you want to disable the batch input (sy-binpt), you can use the addition OPTIONS FROM in call transaction statement.
    It refers to the structure CTU_PARAMS in ABAP dictionary and contains the following components:
    Component
    Meaning
    DISMODE
    Processing mode for batch input processing. Values as for the MODE addition.
    UPMODE
    Processing mode for batch input processing. Values as for the UPDATE addition.
    CATTMODE
    CATT mode for batch input processing. CATT means Computer Aided Testtool. While batch input is mostly used for data transfer, CATT processes are to be viewed as more complex transactions, since they are reusable tests. Values: " " (no CATT mode), "N" (CATT without single screen control), "A" (CATT with single screen control).
    DEFSIZE
    Selection as to whether the screens of the called transaction are displayed in the standard screen size. Values "X" (standard size), " " (current size).
    RACOMMIT
    Selection as to whether the COMMIT WORK statement terminates batch input processing or not. Values: " " (COMMIT WORK terminates processing), "X" ( COMMIT WORK does not terminate processing).
    NOBINPT
    Selection for the symbol field sy-binpt. Values: " " (sy-binpt contains in the called transaction "X"), "X" (sy-binpt contains in the called transaction " ").
    NOBIEND
    Selection for the system field sy-binpt. Values: " " (sy-binpt contains "X" after the end of the batch input data in the called transsaction ) "X" (sy-binpt contains " " after the end of the batch input data in the called transaction).
    In this, if you give NOBINPT as 'X', the system field sy-binpt becomes disabled. You can also set the processing mode and update mode using DISMODE and UPMODE respectively.
    Thanks & Regards,
    T. Prasanna Kumar

  • BDC - not working in 'No Display' mode

    Hi Friends,
    I have written a BDC for TCode O3URV_SS0.I have used CALL TRANSACTION for that.For capturing messages I have used application log.
    In 'N' mode this BDC is not performing properly.For a new set of line item and  a header data it should save that  records and generate a document number.But in 'N' mode the BDC is working for 1st line item only.
    This BDC is working fine in 'A' mode.
    Please help me to solve this problem.

    Moderator message - Welcome to SCN
    But please search before asking - post locked
    Please read [Rules of Engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement], How to post code in SCN, and some things NOT to do... and [Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers] before posting again.
    Rob

  • BDC update MOdes.

    Wht is the UPDATE mode in BDC?What is the imporatance for that.

    <b>A</b> 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.
    <b>S</b> 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.
    <b>L</b> 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.)
    plz  close the thread if got the answer...
    reward if it helps u...
    sai ramesh.

  • Meaning of Update mode L in BDC

    Dear All ,
    I am not able to understand from help the meaning of Update mode 'L' in BDC call transaction . I will be thank full if any body can explain me in simple way

    Hi,
    The three Update Modes of BDC are:
    "A" synchronous update. Updates of called programs are executed in the same way as if in the COMMIT WORK statement the AND WAIT addition was not specified.
    "S: Synchronous processing. Updates of the called programs are executed in the same way as if in the COMMIT WORK statement the AND WAIT addition had been specified.
    "L" Local update. Updates of the called program are executed in such a way as if the SET UPDATE TASK LOCAL statement had been executed in it.
    Regards,
    Anji

  • Screen Resolution problem in BDC

    Hi,
    I am writing a BDC for credit memo creation using FB65 transaction in 4.6b version.
    I am facing BDC problems because of screen resolution. Is there a way to determine the number of lines items that may show up in the table control based on the resolution.
    There is no position button available in 4.6b . also page down is not working.
    Could anyone suggest an alternative?

    Hi,
    Use the below syntax...
    CALL TRANSACTION tcode... OPTIONS FROM opt
    ... OPTIONS FROM opt
    Effect
    Allows you to control processing using the values of the componetns of the structure opt, which must have the ABAP Dictionary type CTU_PARAMS. The components have the following meanings:
    DISMODE
    Display mode (like the MODE addition)
    UPDMODE
    Update mode (like the UPDATE addition)
    CATTMODE
    CATT mode (controls a CATT)
    CATT mode can have the following values:
    ' ' No CATT active
    'N' CATT without single-screen control
    'A' CATT with single-screen control
    DEFSIZE
    Use default window size
    RACOMMIT
    Do not end transaction at COMMIT WORK
    NOBINPT
    No batch input mode (that is, SY-BINPT = SPACE)
    NOBIEND
    No batch input mode after the end of BDC data.
    The components DEFSIZE , RACOMMIT, NOBINPT, and NOBIEND always take the following values:
    'X' Yes
    ' ' No
    If you do not use the OPTIONS FROM addition, the following control parameter settings apply:
    DISMODE
    From addition MODE
    UPDMODE
    From addition UPDATE
    CATTMODE
    No CATT active
    DEFSIZE
    Do not use default window size
    RACOMMIT
    Successful end on COMMIT WORK
    NOBINPT
    Batch input mode active ( SY-BINPT = X
    NOBIEND
    Batch input mode remains active after the BDC data

  • How we will maintain screen resolution for tmaintaining able control in BDC

    how we will maintain screen resolution for tmaintaining able control in BDC. can you give the code or how we have to set it

    Hi,
    You need to use the CTU_PARAM options with the call transaction method.This is used if you would like to do a commit work once call trnasaction is done. This has also got very important property, for example if your Screen resolution is different from others then the screen (Application) will be different that is you'll be having say 5 lines in your screen where as your friend will be having 8 or 10 so your program might fail in this case. If you set variable DEFSIZE as 'X' it will always use the default screen size and hence avoids error.
    Use CALL TRANSACTION 'XXX' OPTIONS FROM w_ctu_params.( type CTU_PARAMS)
    This structure contains the follwing.
    DISMODE : Display mode (like the MODE addition)
    UPDMODE: Update mode (like the UPDATE addition)
    CATTMODE: CATT mode (controls a CATT)
    CATT mode can have the following values:
    ' ' No CATT active
    'N' CATT without single-screen control
    'A' CATT with single-screen control
    DEFSIZE : Use default window size (Here we are handling those transaction by giving default window size)
    RACOMMIT: Do not end transaction at COMMIT WORK
    NOBINPT : No batch input mode (that is, SY-BINPT = SPACE)
    NOBIEND : No batch input mode after the end of BDC data.
    The components DEFSIZE , RACOMMIT, NOBINPT, and NOBIEND always take the following values:
    'X' Yes
    This might help u in better understanding...
    Re: regarding bdc
    Re: ctu_params
    Regards
    Sudheer

  • How to set screen resolution in BDC

    hi pls give info regarding how to set resolution for screen
    thank you
    Ravi

    hi,
    For screen resolution use ctu_params, with default size
    Data : f_option type ctu_params,
    f_option-updmode = 'S'.
    f_option-defsize = 'X'.
    f_option-dismode = 'N'.
    call transaction 'VA01' using bdcdata options from f_option messages into bdcerror.
    CALL TRANSACTION tcode... OPTIONS FROM opt
    ... OPTIONS FROM opt
    Effect
    Allows you to control processing using the values of the componetns of the structure opt, which must have the ABAP Dictionary type CTU_PARAMS. The components have the following meanings:
    DISMODE
    Display mode (like the MODE addition)
    UPDMODE
    Update mode (like the UPDATE addition)
    CATTMODE
    CATT mode (controls a CATT)
    CATT mode can have the following values:
    ' ' No CATT active
    'N' CATT without single-screen control
    'A' CATT with single-screen control
    DEFSIZE
    Use default window size
    RACOMMIT
    Do not end transaction at COMMIT WORK
    NOBINPT
    No batch input mode (that is, SY-BINPT = SPACE)
    NOBIEND
    No batch input mode after the end of BDC data.
    The components DEFSIZE , RACOMMIT, NOBINPT, and NOBIEND always take the following values:
    'X' Yes
    ' ' No
    If you do not use the OPTIONS FROM addition, the following control parameter settings apply:
    DISMODE
    From addition MODE
    UPDMODE
    From addition UPDATE
    CATTMODE
    No CATT active
    DEFSIZE
    Do not use default window size
    RACOMMIT
    Successful end on COMMIT WORK
    NOBINPT
    Batch input mode active ( SY-BINPT = X
    NOBIEND
    Batch input mode remains active after the BDC data

Maybe you are looking for