How To Fix EA871 - IDocs to be processed not found in database


SAP Error Message - Details

  • Message type: E = Error

  • Message class: EA - IDoc Basis Messages

  • Message number: 871

  • Message text: IDocs to be processed not found in database

  • Show details Hide details


  • 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 EA871 - IDocs to be processed not found in database ?

    The SAP error message EA871, which states "IDocs to be processed not found in database," typically indicates that the system is unable to find any IDocs that match the criteria for processing. This can occur in various scenarios, such as during the processing of inbound or outbound IDocs.

    Causes:

    1. IDoc Not Created: The IDoc may not have been created successfully due to issues in the sending system or during the IDoc generation process.
    2. IDoc Status: The IDoc may have a status that prevents it from being processed (e.g., status 51 - "Application document not posted").
    3. Selection Criteria: The selection criteria used in the processing transaction (e.g., WE19, WE20) may not match any existing IDocs.
    4. Database Issues: There may be issues with the database that prevent the retrieval of IDocs.
    5. IDoc Deletion: The IDoc may have been deleted or archived, making it unavailable for processing.
    6. Configuration Issues: Incorrect configuration in the IDoc processing settings or partner profiles.

    Solutions:

    1. Check IDoc Creation: Verify that the IDoc was created successfully in the sending system. You can check the IDoc status in transaction WE02 or WE05.
    2. Review IDoc Status: Look for IDocs with a status that indicates they are ready for processing. If the status is not appropriate, you may need to correct the underlying issue.
    3. Adjust Selection Criteria: Ensure that the selection criteria used in the processing transaction are correct and broad enough to capture the IDocs you want to process.
    4. Database Check: Check the database for any issues. You may need to consult with your database administrator if there are concerns about database integrity or performance.
    5. Reprocess IDocs: If IDocs are in an error status, you may need to reprocess them using transaction BD87 or similar.
    6. Configuration Review: Review the configuration settings for IDoc processing, including partner profiles and message types, to ensure they are set up correctly.

    Related Information:

    • Transaction Codes:
      • WE02: Display IDocs
      • WE05: IDoc List
      • BD87: Reprocess IDocs
      • WE19: Test tool for IDocs
    • IDoc Status Codes: Familiarize yourself with IDoc status codes to understand the state of your IDocs.
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues related to IDoc processing.
    • Monitoring Tools: Use monitoring tools like SAP Solution Manager to keep track of IDoc processing and identify issues proactively.

    If the problem persists after checking these areas, it may be beneficial to consult with your SAP Basis or technical team for further investigation.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant