IDOC Error Status 20 - Error triggering EDI subsystem

Hi Expert
I have articles which have 2 different EAN, (KG & EA) for single store i am getting error , if i generated a IDOC for EA articles, not KG articles.
Kindly suggest me a solution
Regard
Nabil

Hi,
Please check with this link, it could be helpful.
Error in idoc with status 20 "Error triggering EDI Subsystem"

Similar Messages

Error in idoc with status 20 "Error triggering EDI Subsystem"

Dear All,
I have query related to IDOC Status 20.
I am tirggering IDOC with standard t-code from IS-Retail system. I have created two ports a) TRFC port and b)File port .
We are having sending and receiveing application on two different OS i.e one XI on Windows and IS Retail on AIX(Unix). I am not able to send idoc to another system. I am getting these IDOC status in WE05 (STATUS 01 , 30 , 03 , 20 )
Keeping the above fatcs in mind could you please tell me how to remove the error with status 20 "Error triggering EDI Subsystem".

Hi prabhat,
You should have checked the automatic triggering possible at the file port level and the partner profile setting could be 'start subsytem'.
Go to WE21 and do the access test for the file port.
Once you done and find no issues then go to SM59 and test the connection for the RFC destination assigned to the ports.Possibly it has to do with the RFC destination.
Other reasons could be yours is a test client and got refreshed recently.so the production client settings might be causing this error.Check with your basis to get it working.
other reason could be the logical system assigned to the client should be having production client's name.
Check these.
I am sure you should be able to solve this issue.
Thank you.
regards,
karun.M

IDOC : error message 20 : Error triggering EDI subsystem

Hi,
I am creating an extended idoc for WP_PLU message type . I am sending the data from my LS to KU(Customer).
In WE20, I have configured the message type for that KU. I am using an XML port .
The problem is that the Idoc file is getting created properly but it is thowing this message : Error 20 : Error triggering EDI Subsystem.
In WE21 , I have ticked the Start subsytem radiobutton. I am not using any Middleware.It is simple data transfer .
Same thing is working file when I am assigning a File port instead of XML port.
Please help me on this urgently.

Dear All,
Many thanks for all suggestions. Very appreciated it guys.
My problem solved, the issue was actually from the Functional configuration.
After debugging i found out that there's a option to generate a trigger file (related to POS Outbound). If you tick this option then maybe you have to maintain the download path somewhere.
My case is the option was ticked but system can't find the path.
SAP put as error message 20 in the IDOC status.
This maybe can explain also why i still can see my IDOC reached XI and file generated. Since the issue is not really related to any setting in IDOC but more to business configuration.
Best Regards,
Victor.

20:Error triggering EDI subsystem

Dear All.
I am tirggering IDOC with standard t-code(WPMA) from SAP to middleware( It provides Sap Adapter ).
1) I have created TRFC port (SM59).
2) Defined the port(WE21)
3) Defined the Partner Profile(WE21) Outbound IDOC TYPE: wp_ean01
then, I tirgger IDOC with WPMA.
but , the status is :
       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
It is strange that the middleware can receive the data which I send.
What is the problem?

Hi Peter.
First        : The RFC destination is OK, I can test it , the middleware can receive
                 the IDOC data.
Secondly : I define the port(WE21: Transcation RFC).there is another port
                 ( file port) in SAP, but I do not think it can trigger the processing.

Error triggering EDI subsystem

Hi ,
I am getting error - Error triggering EDI subsystem- while posting Idocs in R/3 to XI.
But messages are reaching XI and final XML files also getting generated in outbound location, no issues.
I AM USING PARTNER PROFILE OF TYPE - KU(CUSTOMER)
Following are the status messages i could see in R/3 (tran code-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
Please suggest me how to get rid of this error.

Hi Rajesh,
Check the ports (we21), RFC destinations, Partner profiles are defined correctly or not.
Regards
Kannaiah

Error triggering EDI subsystem : Error#20

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

Rajesh,
While creating the Partner Profile, have you 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.
Regards
Bhavesh

Error Triggering EDI Subsystem 20

When we try to send IDOCs from SAP to XI system using WPMI transaction, we are getting status 20 ( Error Triggering EDI Subsystem).
What should be done to overcome this issue?
Regards
Raj

Hi Rajagopal,
This thread solves your question...
Error in idoc with status 20 "Error triggering EDI Subsystem"
Can you please check if the PORT and LS details in the control record are correct
cheers
Prashanth
P.S Please mark helpful answers

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

Error triggering EDI subsystem (GIS): Process request without transaction.

I'm trying to configure SAP to trigger the EDI subsytem (Sterling's GIS). I'm getting error status "20":
Error for Remote Function Call with port "GIS"
Error message from RFC_REMOTE_EXEC
Process request without transaction. TID is empty.
Does anyone know what this means?
Thank you,

Here is the SAPSuite Adapter Config in GIS:
Service Name                     COMP_SapSuiteALE
Service Type                     SAP Suite Adapter
Description                      ALE based IDoc XFer
System Name                      COMP_SapSuiteALE
Group                            None provided
SAP Integration Mode             ALE based IDoc
SAP system is loadbalanced       No
Client                           300
User                             sapadmin
Language                         EN
Code Page                        1100
Start RFC Server automatically   Yes
RFC Server Instances             1
Program ID                       GISR3D
Outbound Process to start        COMP_SAPOutboundALE
Outbound Encoding                UTF8
Wait for synchronous RFC Outbound response   Yes
Response timeout (seconds, 0=unlimited)   0
Delete TIDs automatically        Yes
Delete TIDs after (days)         30
Register Remote Function Calls (BAPI or RFC Mode only)   None (for IDoc modes or BAPI/RFC Inbound)
Filter online RFC list by        None provided
Use hard max. connections limit ( Off = soft limit )   No
Max. Connections                           4
Soft Limit Delay Time (seconds)            20
Connection Check Interval (seconds)        30
Connection Idle Time (seconds)             240
Close session after maximum session time   No
Max. Session Time (minutes)                20
User                                       admin

Idoc Outbound Status Error

Hello everybody,
I have an interface that sends and Idoc to an R/3 system and I have it on Status "Processed" but in Outbound Status "System Error" with red flag in SXMB_MONI in PI, but I can't see no dumps neither in PI or R/3, so message in queues I turned on the trace in ST01 and I can't the RFC call that PI should do to R/3 to send the Idoc, I think is about roles and security oft he communication user that exists in R/3, but I'm not sure what roles it should have to allow the Idoc to go thru, any suggestions?, thanks in advance.
Regards,
Oscar

You dont' have enough permission. SAPALL try with..
check this one SAP Note Number: 460089
Edited by: Anand on Dec 4, 2008 7:03 PM

SRM PO Changes Error Status - Error in Process (SRM 4.0 and ECC 5.0)

Hi All,
I created PO in SRM from Sourcing (Shopping Cart) and it is replicated to Back End (ECC 5.0). But I did not post GR or Invoice Verication with reference to PO.
When I am trying to change PO in SRM (SRM Webbrowser - Processing PO) like Quantity, I am receiving the PO status as Error in Process.
Please let me know do I need to configure anything for this issue or need to implement OSS Note/BADI.
Thanks a lot in advance for helping me.
Best Regards,
Sudarsan

got solution

Idoc gets status 20 after status 03

I'm using an RFC transaccional port in R/3 , i am sending the idoc of bonus buy (WPDBBY), i send the idoc using the transacion WPMA, after that in transaction WE02 i see that the idoc has the status 20, but before this status the idoc got the status 03 (IDoc sent to R/3 System or external program)...
The idoc WPDBBY is correctly processed in XI..
¿Why i'm getting the error in status 20?
Thanks

Hi,
The IDOC status 20 describes: Error triggering EDI subsystem
For Confirmation purpose, check this IDCO number in XI IDX5 TC.
If the IDOC is successfully reached by XI, try for SAP Notes to change the status.
Thanks,
Boopathi
Edited by: Boopathi Thangavel on Sep 19, 2008 6:32 AM

Idoc with status 68

Hi,
Can any one tell me the reason for idoc status as 68.......in which case the system will show me the idoc status as 68
Thanks,
Shilpa

IDoc status Description
Outbound values :-->
00 Not used, only R/2
01 IDoc generated
02 Error passing data to port
03 Data passed to port OK
04 Error within control information of EDI subsystem
05 Error during translation
06 Translation OK
07 Error during syntax check
08 Syntax check OK
09 Error during interchange handling
10 Interchange handling OK
11 Error during dispatch
12 Dispatch OK
13 Retransmission OK
14 Interchange Acknowledgement positive
15 Interchange Acknowledgement negative
16 Functional Acknowledgement positive
17 Functional Acknowledgement negative
18 Triggering EDI subsystem OK
19 Data transfer for test OK
20 Error triggering EDI subsystem
21 Error passing data for test
22 Dispatch OK, acknowledgement still due
23 Error during retransmission
24 Control information of EDI subsystem OK
25 Processing despite syntax error (outbound)
26 Error during syntax check of IDoc (outbound)
27 Error in dispatch level (ALE service)
28 Not used
29 Error in ALE service
30 IDoc ready for dispatch (ALE service)
31 Error - no further processing
32 IDoc was edited
33 Original of an IDoc which was edited
34 Error in control record of IDoc
35 IDoc reloaded from archive
36 Electronic signature not performed (timeout)
37 IDoc added incorrectly
38 IDoc archived
39 IDoc is in the target system (ALE service)
40 Application document not created in target system
41 Application document created in target system
42 IDoc was created by test transaction
Inbound Values::-->
50 IDoc added
51 Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc copy from R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction

EDI Subsystems vs XI - functional differences

I have seen from posts in this forum and other resources that it is possible to use XI as an EDI subsystem (please correct me if that is incorrect). However, what I would like to know is what functionality is missing if you do that.
Also, I thought that it was the responsibility of the EDI subsystem to update the status of the IDocs as appropriate. If true, does XI also do the same thing?

Hi Praveen,
I have been working with IDocs for a few years now, and from what I understand, it is the responsibility of the EDI subsystem to update the status section of the IDoc (the EDIDS status record); you know, status such as
18 - Triggering EDI subsystem OK
22 - Dispatch OK acknowledgement still due.
So does XI actually update the IDocs with this status information?
The point is: if I use XI as an EDI subsystem, and it doesn't do that, I cannot tell what has happened to the IDoc when I use the R/3 reporting tools to check the status of all the IDocs.
I know that XI has its own message monitoring built in, but I still haven't had a clear answer regarding updating of IDoc status per se.
Kind Regards,
Tony.

Sarting the EDI Subsystem

Hi All
I have to determine whether i have to start my EDI sub system immediately or not,But when i checked the Transaction WE20 Partner profiles- output mode.
I couldn't find any thing to make an entry to have a control over EDI Subsystem (Whether to start immediately or later)
Can ane one throw some views towards this..
Appreciate your answers.
Thanks
@run.

Hi Radhu Shankar G
To solve your problem
Modify the Condition record for you output type for that customer
with Dispatch time is equal to 1 - Send with periodically scheduled job
Now idoc won't be send ......it will be in unprocessed state....
u can run the job when ever u want idoc to be posted to edi subsystems...
I hope it helps to resolve the issue
Ramesh

IDOC Error Status 20 - Error triggering EDI subsystem

Similar Messages

Maybe you are looking for