cancel
Showing results for 
Search instead for 
Did you mean: 

Entry in outbound table not found E0 400

Former Member
0 Kudos

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.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

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

Regards,

Janaina

Former Member
0 Kudos

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).
  endif.

Former Member
0 Kudos

Hi Vishnu,

Thanks for your reply.

my settings are fine.

i have the same settings in dev sys..but when i am trying to make teh same in quality...i got this error.

pls suggest..

Former Member
0 Kudos

As you can see from the SELECT query above, the error message is given only if the SELECT fails.

What you can do is open EDIDC table in SE16 for your IDoc number and compare the values of the fields that are being checked in the above SELECT query with corresponding fields in EDP13 for your message type and partner. You will definitely see some or other field not matching

Former Member
0 Kudos

hi vishnu,

i have already checked the table EDP13.

idoc type i have assigned to partner profile and the idoc triggered are different...and

port name even did not come in idoc...

but the same settings works fine in dev system.

what might be the problem in quality system. any clues? pls?

Former Member
0 Kudos

You need to have the IDoc type and message type from control record matching with outbound partner profile parameter in WE20. Otherwise you will get this error. If this error is not coming in your dev system it is because there is a partner profile outbound parameter that matches with the IDoc control record there.

Former Member
0 Kudos

thank u vishnu for ur reply.

both the systems are having the same partner profile settings maintained.

i have checked in both of my systems.

partner profiles are good. do i have to mainatin them in bd64.

nabheetscn
Active Contributor
0 Kudos

As you are saying idoc triggered are different please check the whole config first.

Former Member
0 Kudos

hi,

idoc types are different in dev and quality for the same config...

i have checked it............

can u please tell me the configuration in case if i miss out anywhere...

thanks..

Former Member
0 Kudos

Hello.

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