Skip to Content
0
Jun 04, 2009 at 11:40 AM

CALL TRANSACTION 'OOET' not working.

101 Views

Hello friends,

Im using Call transaction on a program and captured all message on i_messtab, that's ok but there is somethigs rare cuz the right message never is captured for call transaction.

Im using Call transaction to OOET when I create new data by funcional way i can see the message " new data is created" but on call transaction never i see that.

Who of you have seen this kind of situation or i have todo somethings special?

Here my code:

  CALL TRANSACTION 'OOET'  USING bdcdata  MODE 'A'
                               UPDATE 'S'
                                 MESSAGES INTO i_messtab.


  REFRESH bdcdata.

  LOOP AT i_messtab.
    SELECT SINGLE * FROM t100 WHERE sprsl = i_messtab-msgspra
                              AND   arbgb = i_messtab-msgid
                              AND   msgnr = i_messtab-msgnr.
    IF sy-subrc = 0.
      l_mstring = t100-text.
      IF l_mstring CS '&1'.
        REPLACE '&1' WITH i_messtab-msgv1 INTO l_mstring.
      ENDIF.
      IF l_mstring CS '&2'.
        REPLACE '&2' WITH i_messtab-msgv2 INTO l_mstring.
      ENDIF.
      IF l_mstring CS '&2'.
        REPLACE '&3' WITH i_messtab-msgv3 INTO l_mstring.
      ENDIF.
      IF l_mstring CS '&2'.
        REPLACE '&4' WITH i_messtab-msgv4 INTO l_mstring.
      ENDIF.
      IF l_mstring CS '&'.
        REPLACE '&' WITH i_messtab-msgv1 INTO l_mstring.
        REPLACE '&' WITH i_messtab-msgv2 INTO l_mstring.
        REPLACE '&' WITH i_messtab-msgv3 INTO l_mstring.
        REPLACE '&' WITH i_messtab-msgv4 INTO l_mstring.
      ENDIF.
      CONDENSE l_mstring.  " l_mstring los mensajes de error
      CLEAR i_mensajes.
      MOVE l_mstring TO i_mensajes-message.
      APPEND i_mensajes.
    ENDIF.
  ENDLOOP.

Another doubt, when in BDCDATA i have more that one Register just the process took one of them and finish, call transaction is just for one by one?

Best Regards,

emachado

Edited by: Julius Bussche on Jun 9, 2009 5:40 AM