Problem Capturing BDC Error Msgs

[Former Member]

Hi,

I am facing a problem in capturing BDC Error Msgs when using

CALL TRANSACTION 'MF42N' USING BDCDATA

MODE FMODE

UPDATE 'L'

MESSAGES INTO MESSTAB.

after which to get the msg I used the following coding

LOOP AT MESSTAB WHERE MSGTYP = 'E'.

CALL FUNCTION 'MESSAGE_TEXT_BUILD'

EXPORTING

MSGID = MESSTAB-MSGID

MSGNR = MESSTAB-MSGNR

MSGV1 = MESSTAB-MSGV1

MSGV2 = MESSTAB-MSGV2

MSGV3 = MESSTAB-MSGV3

MSGV4 = MESSTAB-MSGV4

IMPORTING

MESSAGE_TEXT_OUTPUT = W_TEXTOUT.

MESSAGE E126 WITH W_TEXTOUT.

ENDLOOP.

Now the problem is that when I run the BDC - MESSTAB does not contain all the error msgs which is shown

In the standard transaction "MF42N" run. and more over the msg type differs from standard run and the msgs in "MESSTAB"

Please Help me .

Thanks in Advance

S.Sathish

[Former Member]

see the following example

DATA CTU_PARAMS LIKE CTU_PARAMS.
DATA:   MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
 

CALL TRANSACTION 'T.CODE' USING BDCDATA OPTIONS FROM CTU_PARAMS MESSAGES  INTO MESSTAB.

[Former Member]

thanks for the respone .

but still i have another problem.

I my company we have given the user Z screen for "MF42N" posting.

where in the BDC takes place in back ground

using mode "N".

but its not possible to give Mode when options is used.

and i do not want the user to see the error log .

instead to capture the error msg from the log and display the relavent msg alone

[Former Member]

Hi,

While using OPTIONS also you can pass the Mode

opt-nobinpt = 'X' .
opt-dismode = 'N'.

call transaction 'F-02' using bdcdata   options from opt messages into messtab.

Regards

Vinod

[Former Member]

Thanks Vinod.

but still my primary issue is not address.

I am not able to fetch the error msgs which is shown in the error log in the standard transaction.

Is it possible to retrive the messages into MESSTAB from the MSG log which is shown after the standard transaction run.

Error msg from msg log in standard transaction run is not captured in BDC - MESSTAB.

what is the soultion for it?

[Former Member]

Please Help me in solving the Issue.

[Sandra_Rossi]

Messages should be captured, but the issue is maybe that you only select E type messages. Maybe the "error messages" you mention are of type S, but displayed like E. So, could you look at all messages in MESSTAB?

Moreover, sometimes, the transaction may not behave the same way interactively and with call transaction. You may check whether the message is really output by running call transaction in A mode (display each screen).

Last thing, call transaction only captures messages that are output by MESSAGE statement (without INTO keyword). If these messages appear in a popup for example, you won't be able to capture them.

[Former Member]

This message was moderated.

[Former Member]

This message was moderated.