Skip to Content
avatar image
Former Member

Entry in outbound table not found E0 400

Hi all,

Can anyone please help me with the below error which i am facing in ALE IDOCS.

status 29: Entry in outbound table not found E0 400

I am unable to see my port name in the created IDOC and the basic type is incorrectly called.

may I know what settings need to be verified.

Thanks in advance.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Dec 19, 2011 at 07:16 PM

    SAP checks the IDoc control record for outbound IDoc against EDP13 (outbound partner profile table). EDP13 is updated when you create outbound partner profile parameter in WE20

    Check if you have created the partner profile outbound parameter in WE20 correctly to match your outbound IDoc control record.

    SAP checks partner number, port, partner function of the receiver along with message type, message code and message function. They all should match between WE20 outbound partner profile parameter for your message type and the IDoc control record (EDIDC) segment.

    This is the SAP code that throws the error message you mentioned


    read table q_edidc index 1.
      select single * from edp13
                      where rcvprn eq q_edidc-rcvprn
                      and   rcvprt eq q_edidc-rcvprt
                      and   rcvpfc eq q_edidc-rcvpfc
                      and   mestyp eq q_edidc-mestyp
                      and   mescod eq q_edidc-mescod
                      and   mesfct eq q_edidc-mesfct
                      and   test   eq q_edidc-test.
      if sy-subrc ne 0.
        concatenate q_edidc-rcvprn '/' q_edidc-rcvprt '/' q_edidc-rcvpfc '/'
                    q_edidc-mestyp '/' q_edidc-mescod '/' q_edidc-mesfct '/'
                    q_edidc-test into text.
        condense text no-gaps.
        message a400(E0) with text(50).

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member


      I have an issue where I receive the same error message except the fact my iDoc doesn't get created. In fact E400 error is displayed in the log of the failed RD04 output. I have provided many other details HERE.

      To be very honest I suspect that I may face an undocumented ABAP code is messing with my work: what is the program containing the above code and how can I test it?

      Thank you in advance

  • avatar image
    Former Member
    Jun 11, 2016 at 07:43 PM

    Hi ALL,

    For this type os issues check note:

    2005372 - Error messages after system refresh procedure (RSAR, E0)

    and Blog Post:

    RSAR, E0 errors after system refresh or BDLS



    Add comment
    10|10000 characters needed characters exceeded