20: Error triggering EDI subsystem

[Former Member]

Hi All,

Getting error – 20: Error triggering EDI subsystem – while triggering IDOC for XI. But, messages are getting posted into XI and final XML files also getting generated in outbound location.

I am using partner profile of type customer in R/3.

Following are the status messages I could see in WE05.

20 Error triggering EDI subsystem

03 Data passed to port OK

IDoc sent to SAP system or external program

30 IDoc ready for dispatch (ALE service)

Receiver exists , No filters , No conversion , Version conversion

01 IDoc generated

If any one could come up help diagnose this probem it will be highly appreciated and rewarded as well.

[Former Member]

hI, we are also facing same issue. can u please let us kknow how the issue got resolved?

[Former Member]

Please check the note no 562925 for the error status 20, we resolved using this note..hope this helps

[Former Member]

Hi,

Check in partner profile WE20 for the partner that you re sending the invoice.Make sure the setting radio button clicked start subsystem.

Also check RFC destination connection.Find out this is the first time ayou are trying to send some data to EDI or you have been communicating with EDI from long time.If you are well established coneection b/w EDI and SAP from long time then just check ur partner profile as suggested

Pls reward if helpful

ramesh

[Former Member]

Hi,

The error message

Error triggering EDI subsystem with code 20 indicates that

While creating the Partner Profile, you have added something in the EDI Standard tab?

By default if the requirement is only to post an idoc to Xi, you need not add anything to the EDI standard tab for your outbound Idoc entry in We20.

also Please can you check if the PORT and LS details in the control record are correct.

refer

thanks

Swarup

[Former Member]

Well swarup, i have not maintanied anything in EDI standard tab and am using RFC port everything is configured correctly...

[nisarkhan_n]

This is mainly when R/3 is not able to locate the receivng systems....you said IDOC are coming into XI right?

cehck this

check for entries in sm58

If entries exist in SM58, look for Message Type. If message type exist and Run the Program "RSARFCEX"

If after the RSARFCEX program has ran and IDocs are not in SM58, issue should be solved. Validate in receiving system via WE05 that the IDoc was received. If IDoc is still stuck in SM58, check RFC connection. Go to SE37, enter function module RFC_PING.

Note: In most of the case we'll not have access to SM59 to test the RFC Connection.

Hit test button, Enter RFC destination (the interface system of the IDoc). NOTE: when entering RFC destination, keep in mind the field is case sensitive.

Hit execute button

If function module fails, there is an RFC issue. Contact team, which creates the RFC Destination.

[nisarkhan_n]

where are u getting this error then?

[Former Member]

Once the delivery is created and PGI is done..an idoc is triggered it does send the file to the XI destination but it gives that 20 error status..Configuration for output type done is as follows..

Transmission medium is 6(EDI) and it is maintained same in all the places..