topic Re: bdc in Application Development and Automation Discussions

bdc

Former Member — Thu, 07 Aug 2008 05:26:54 GMT

hello sap gurus,

Can any one tell me how we come to know whether call transaction processed or not ?

if the system suddenly crushed how we know it processed or not ?

regards,

vijaya.

Re: bdc

Former Member — Thu, 07 Aug 2008 05:31:33 GMT

Each call transaction gives you the message back in the message table. Due to you call transaction, some document has been created or changed.

Try to search for the message with type 'S' and has the same message number which is getting triggered when you have created the document.

Regards

Divya

Re: bdc

Former Member — Thu, 07 Aug 2008 05:36:13 GMT

hi,

You can Check the status of the CALL Transaction Method by using BDCMSGCOLL structure.

The Messages are stored in the table type of BDCMSGCOLL.

You can Retrieve those messages and check the status.

Regards

Sumit Agarwal

Re: bdc

Former Member — Thu, 07 Aug 2008 05:39:59 GMT

This message was moderated.

Re: bdc

Former Member — Thu, 07 Aug 2008 05:44:30 GMT

Can any one tell me how we come to know whether call transaction processed or not ?

if the system suddenly crushed how we know it processed or not ?

what do you mean by system crushed?is it for proccesing abort?if yes than see the transaction for which you created BDC else see BDCMSGCOLL table for message.

Amit.

Re: bdc

Former Member — Thu, 07 Aug 2008 05:45:45 GMT

Hii!

To get the information about success or failure of call transaction

You have to declare a workarea and internal table of type bdcmsgcoll in your program. All the messages will be stored in this internal table.

and call the transaction in this way


CALL TRANSACTION '<tcode>' USING t_bdcdata MODE 'N' MESSAGES INTO <internal_tab>.

Now loop the internal table of type bdcmsgcoll and within it call the function

FORMAT_MESSAGE


LOOP AT <internal_tab INTO <workarea>.
  CALL FUNCTION 'FORMAT_MESSAGE'
   EXPORTING
     id              = fs_msg-msgid
     lang            = sy-langu
     no              = fs_msg-msgnr
     v1              = fs_msg-msgv1
     v2              = fs_msg-msgv2
     v3              = fs_msg-msgv3
     v4              = fs_msg-msgv4
   IMPORTING
     msg             = w_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.
  ENDIF.

  WRITE: / w_msg.
ENDLOOP.

Regards

Abhijeet

Re: bdc

Former Member — Thu, 07 Aug 2008 05:46:09 GMT

Hi Vijaya,

We can get the information regarding CALL TRANSACTION from the message table of tyep BDCMSGCOLL.

All types of messages are stored in the table type of BDCMSGCOLL.

Regards,

Chandra Sekhar

Re: bdc

Former Member — Thu, 07 Aug 2008 05:53:01 GMT

Hi Vijaya.

I would like to suggest,

I cannot judge the situation with respect to system crash.

But, The Transaction - STAD - Workload Monitor

Helps in getting the Time, Memory used, Transfer bytes as well as the detailed analysis in relation with Transaction also.

The log file details can be downloaded by the DOWNLOAD button in Text file.

Hope that's usefull.

Good Luck & Regards.

Harsh Dave