How To Fix EA813 - Control record of IDoc with number & not found

SAP Error Message - Details

• Message type: E = Error

• Message class: EA - IDoc Basis Messages

• Message number: 813

• Message text: Control record of IDoc with number & not found

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 EA813 - Control record of IDoc with number & not found ?

  The SAP error message EA813 indicates that the control record of an IDoc (Intermediate Document) with a specific number could not be found. This error typically occurs when there is an issue with the IDoc processing, and it can be caused by several factors. Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  IDoc Not Created: The IDoc may not have been created successfully, or it may have been deleted before processing.
  Incorrect IDoc Number: The IDoc number referenced in the error message may be incorrect or malformed.
  Database Issues: There may be issues with the database that prevent the IDoc control record from being accessed.
  IDoc Status: The IDoc may be in a status that does not allow it to be processed (e.g., it may be in a status that indicates it has been processed or is in error).
  Transport Issues: If the IDoc is being sent between different systems (e.g., from a development to a production system), there may be transport issues or configuration problems.
  
  Solutions:
  
  Check IDoc Status: Use transaction code WE02 or WE05 to check the status of the IDoc. Look for the IDoc number mentioned in the error message and verify its status.
  Reprocess IDoc: If the IDoc is found but in an error status, you can try to reprocess it using transaction code BD87.
  Verify IDoc Creation: Ensure that the IDoc was created successfully in the first place. Check the application logs or the relevant transaction that should have generated the IDoc.
  Check for Deletion: Ensure that the IDoc has not been deleted. If it has been deleted, you may need to regenerate it.
  Database Consistency: Check for any database inconsistencies. You may need to run database consistency checks or consult your database administrator.
  Review Configuration: If the IDoc is being sent between systems, review the configuration settings in transaction code WE20 (partner profiles) and ensure that the settings are correct.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  IDoc Structure: Understand the structure of IDocs, including control records, data records, and status records.
  Transaction Codes:
  
  WE02/WE05: Display IDocs
  BD87: Reprocess IDocs
  WE20: Partner Profiles
  
  
  SAP Documentation: Refer to SAP Help documentation for detailed information on IDocs and error handling.
  Monitoring Tools: Use monitoring tools like SAP Solution Manager for more comprehensive monitoring and troubleshooting of IDoc processing.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.