Skip to Content
author's profile photo
Former Member

few more basic doubts in ABAP

Hi Floks,

I have few doubts in ABAP programming could please clarify that ..

1. how to handle error messages in Call transaction and Call Session method .

2. which logic can be used to handle the table control in BDC method . when table control required ? let me give few transction related to table control of BDC.

3. what is structure of BDC DATA ? what is diffrence between BDC Session and Call Transaction method in programming steps ?

4.how many message types available ? what are they ?

5.when call transction or Call session can be used ? how to decide which method is best for requirement ?

could you please help me out . if u have any material or links forward to sunithadf@gmail.com.

Good Rewards for best answers

Thanks ,

Sunitha

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • author's profile photo
    Former Member
    Posted on Sep 29, 2007 at 04:14 AM

    Here are the answers to your questions.

    1. how to handle error messages in Call transaction and Call Session method .

    --> In Call transaction, if you see the command, messages are populated into an internal table. You need to read last record of this table. Using Function module FORMAT_MESSAGE, you can get details of the message. For session method, session gets created and status of session can be seen in transaction SM35. You can process erroneous sessions from here.

    2. which logic can be used to handle the table control in BDC method . when table control required ? let me give few transction related to table control of BDC.

    --> Check these links which explain in detail with examples.

    bdc---table-control

    in-bdc-table-control

    3. what is structure of BDC DATA ? what is diffrence between BDC Session and Call Transaction method in programming steps ?

    -->PROGRAM - Program Name

    DYNPRO - BDC Screen number

    DYNBEGIN - BDC screen start (Flag)

    FNAM - BDC Field name

    FVAL - BDC Field value

    ______________________________

    4.how many message types available ? what are they

    -->

    A (Abend) Termination

    E (Error) Error

    I (Info) Information

    S (Status) Status message

    W (Warning) Warning

    X (Exit) Termination with short dump

    5.when call transction or Call session can be used ? how to decide which method is best for requirement ?\

    --> These threads discuss the same

    session-method

    difference-between-session-method-and-call-transac

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 29, 2007 at 04:39 AM

    1) by using BDCMSGCOL structure u have to define one internal table get all the error records into this after that u have to call function FORMAT_MESSAGE.

    data : begin of msgtab occurs 0.

    include structure bdcmsgcol.

    data : end of msgtab.

    CALL TRANSACTION 'tcode' using itab mode e/a/n udate a messages into bdcmsg.

    in session methad by default it have log file u can process all the records in SM35

    2)perform bdc_field using 'bdc_okcode' '=p+' this predefined subroutine u have to call when dealing with table control in BDC. ex XK01 creation of vendor

    3)see this in SE11

    program

    dynpro

    dynbegin

    fieldname

    fieldvalue

    are fields in this structure

    4) error E( gives error message control remains in until user gives correct input)

    abend A (control terminates current program comes to initial screen)

    information I ( gives information)

    warning w( gives warning message)

    exit X (exits the program) leads to short dump analysis

    5) if ur uploading large volume of masterdata better to choose for session method.

    session method doesnt returns SY-SUBRC.

    if ur uploading small amount of transactional data better to go for call transaction

    comparitively it is faster than session method.

    reward for useful points

    regards

    Nagesh.Paruchuri

    Add comment
    10|10000 characters needed characters exceeded