How To Fix E1420 - Trigger file created, but IDocs still have old status

SAP Error Message - Details

• Message type: E = Error

• Message class: E1 - Messages for IDoc Basis

• Message number: 420

• Message text: Trigger file created, but IDocs still have old status

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message E1420 - Trigger file created, but IDocs still have old status ?

  The SAP error message E1420, which states "Trigger file created, but IDocs still have old status," typically indicates an issue with the processing of IDocs (Intermediate Documents) in the SAP system. This error can occur in scenarios where IDocs are expected to be processed or updated, but they remain in their previous status, preventing further processing.
  Causes:
  
  IDoc Processing Issues: The IDocs may not have been processed correctly due to errors in the application logic or configuration.
  Status Update Delay: There may be a delay in the status update of the IDocs, possibly due to background job processing or system performance issues.
  Configuration Errors: Incorrect configuration in the IDoc processing settings or partner profiles can lead to issues in status updates.
  Error in the Trigger File: The trigger file that is supposed to initiate the processing of IDocs may not be functioning correctly or may not be processed as expected.
  Network or Connectivity Issues: If the IDocs are being sent to an external system, network issues could prevent successful transmission and status updates.
  
  Solutions:
  
  Check IDoc Status: Use transaction code WE02 or WE05 to monitor the status of the IDocs. Look for any errors or warnings that may indicate why the IDocs are not being processed.
  Reprocess IDocs: If the IDocs are in an error status, you can attempt to reprocess them using transaction code BD87 or by using the "Reprocess" option in WE02/WE05.
  Review Application Logs: Check the application logs (transaction SLG1) for any related error messages that could provide more context on the issue.
  Verify Configuration: Ensure that the IDoc processing configuration and partner profiles are set up correctly. This includes checking the message type, process code, and other relevant settings.
  Check Background Jobs: If IDoc processing is scheduled as a background job, verify that the job is running successfully and that there are no issues with job scheduling.
  Monitor System Performance: If there are performance issues in the SAP system, it may affect IDoc processing. Monitor system resources and performance metrics.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  IDoc Status Codes: Familiarize yourself with the various IDoc status codes (e.g., 03 for "Data passed to port OK," 12 for "IDoc is being processed," etc.) to better understand the current state of your IDocs.
  Transaction Codes: Common transaction codes for IDoc processing include:
  
  WE02: Display IDoc
  WE05: IDoc List
  BD87: Reprocess IDocs
  SLG1: Application Log
  
  
  SAP Documentation: Refer to SAP Help documentation for detailed information on IDoc processing and troubleshooting.
  
  By following these steps, you should be able to identify the root cause of the E1420 error and take appropriate action to resolve it.