Skip to Content
author's profile photo Former Member
Former Member

type of error in the log file while using using call transaction mode u2018Eu2019

Hi Gurus,

Please Answer for this qusetion urgently

what type of error exactly you will be seeing in the log file while using call transaction mode u2018Eu2019?

Thanks/

Radha.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 17, 2008 at 04:24 AM

    "E" Display of screens only if an error occurs

    \[removed by moderator\]

    Regards

    Anbu

    Edited by: Jan Stallkamp on Jun 17, 2008 6:26 PM

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      The error would be like if the screen field name is not proper or the data which is to be uploaded is not proper or if the proper screen number is not provided then all those errors would be captured in error log.

  • author's profile photo Former Member
    Former Member
    Posted on Jun 17, 2008 at 04:29 AM

    Hi,

    The error messages will be captured in the error log only if an error occurs while uploading the data through BDC.If you run it in the foreground it will show you only those screens where error has occured.If there is no error it won't show anything.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 17, 2008 at 04:33 AM

    Hi,

    Can you be clear.

    In call transaction , no error logs are created, you have to handle the errors explicitly using the structure BDCMSGCOLL.

    Whenever you use E mode then if the transaction encounters any of the errors i.e. data type mismatching or invalid values etc, it will stop at that screen.

    You can handle the errors in call transaction in the following method.

    create a table using the structure BDCMSGCOLL.

    then

    loop at ......

    .

    .

    .

    CALL TRANSACTION 'XK01' USING I_BDCDATA MODE 'N' UPDATE 'S' MESSAGES INTO I_MESGTAB.

    .

    .

    endloop.

    SORT I_MESGTAB BY MSGID MSGV1 ASCENDING.

    DELETE ADJACENT DUPLICATES FROM I_MESGTAB.

    LOOP AT I_MESGTAB.

    CALL FUNCTION 'FORMAT_MESSAGE'

    EXPORTING

    ID = I_MESGTAB-MSGID

    LANG = I_MESGTAB-MSGSPRA

    NO = I_MESGTAB-MSGNR

    V1 = I_MESGTAB-MSGV1

    V2 = I_MESGTAB-MSGV2

    V3 = I_MESGTAB-MSGV3

    V4 = I_MESGTAB-MSGV4

    IMPORTING

    MSG = MESG1.

    IF I_MESGTAB-MSGTYP = 'S' .

    WA_SUCCMESG-MESG = MESG1.

    APPEND WA_SUCCMESG TO I_SUCCMESG.

    else IF I_MESGTAB-MSGTYP = 'E' .

    WA_ERRMESG-MESG = MESG1.

    APPEND WA_ERRMESG TO I_ERRMESG.

    ENDIF.

    ENDLOOP.

    Hope this is clear.

    Thanks and Regards.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.