How To Fix ESH_EX087 - Customized extraction packagesize cannot be read from backend system

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_EX - Extraction

• Message number: 087

• Message text: Customized extraction packagesize cannot be read from backend system

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 ESH_EX087 - Customized extraction packagesize cannot be read from backend system ?

  The SAP error message ESH_EX087 indicates that the customized extraction package size cannot be read from the backend system. This error typically occurs in the context of SAP Enterprise Search or when working with SAP BW (Business Warehouse) and can be related to issues with the configuration or communication between the systems.
  Causes:
  
  Configuration Issues: The extraction settings in the backend system may not be properly configured, leading to the inability to read the package size.
  Authorization Problems: The user executing the extraction may not have the necessary authorizations to access the required data or settings in the backend system.
  System Connectivity: There may be issues with the connection between the frontend and backend systems, such as network problems or incorrect RFC (Remote Function Call) settings.
  Backend System Status: The backend system might be down, or there could be issues with the data source that prevent it from providing the required information.
  Version Compatibility: There may be compatibility issues between the versions of the systems involved, especially if one system has been upgraded or patched.
  
  Solutions:
  
  Check Configuration: Review the extraction configuration in the backend system to ensure that the settings for the extraction package size are correctly defined.
  Verify Authorizations: Ensure that the user has the necessary authorizations to perform the extraction. This may involve checking roles and permissions in both the frontend and backend systems.
  Test Connectivity: Use transaction codes like SM59 to check the RFC connections between the systems. Ensure that the connections are correctly configured and that the backend system is reachable.
  Check Backend System Status: Verify that the backend system is operational and that the relevant data sources are available. You can check system logs for any errors or issues.
  Review System Versions: Ensure that both systems are compatible in terms of versions and patches. If there are discrepancies, consider aligning the versions or applying necessary updates.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to the error message ESH_EX087 for any specific patches or updates that may address the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Documentation: Review the official SAP documentation for Enterprise Search and data extraction processes to ensure that all steps are being followed correctly.
  
  If the issue persists after trying the above solutions, it may be beneficial to involve your SAP Basis team or SAP support for further investigation.