Do you have any question about this error?
Message type: E = Error
Message class: ESH_IEF_MSG - Import/Export Framework
Message number: 138
Message text: Import of SW Comp. not possible (create incident BC-EIM-ESH)
The automated software component import cannot be processed.
System table ESH_OM_TRANS is incomplete (can even be empty).
At least the following record is missing/incomplete:
OBJ_NAME = "&V1&"
Create an incident for component BC-EIM-ESH and ask SAP to repair
content of data base table ESH_OM_TRANS.
For details have a look at note 2354994.
The table ESH_OM_TRANS shall never be empty. Especially a line for
OBJ_NAME = 'ESH_OM_SYSRELD' shall allways be in place.
Error message extract from SAP system. Copyright SAP SE.
ESH_IEF_MSG138
- Import of SW Comp. not possible (create incident BC-EIM-ESH) ?The SAP error message ESH_IEF_MSG138 indicates that the import of a software component is not possible, and it suggests creating an incident with the component BC-EIM-ESH. This error typically occurs in the context of SAP Enterprise Search or related components when there are issues with the import process of software components.
Causes:
- Missing Dependencies: The software component you are trying to import may have dependencies that are not met. This could be due to missing other components or incorrect versions.
- Version Incompatibility: The version of the software component you are trying to import may not be compatible with the existing components in your SAP system.
- System Configuration Issues: There may be configuration issues in your SAP system that prevent the import from proceeding.
- Transport Issues: If the software component is being imported via a transport request, there may be issues with the transport itself, such as it being incomplete or corrupted.
- Authorization Issues: The user performing the import may not have the necessary authorizations to complete the operation.
Solutions:
- Check Dependencies: Verify that all required dependencies for the software component are present and correctly installed in your system.
- Version Compatibility: Ensure that the version of the software component you are trying to import is compatible with your current SAP system version.
- Review Configuration: Check the system configuration settings to ensure that they are correct and that there are no conflicts.
- Transport Request: If applicable, check the transport request for completeness and integrity. You may need to re-import or recreate the transport request.
- User Authorizations: Ensure that the user performing the import has the necessary authorizations to execute the operation.
- SAP Notes: Search for relevant SAP Notes that may address this specific error message or provide guidance on resolving it.
Related Information:
By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
ESH_IEF_MSG137
Select a file path for upload
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_IEF_MSG136
Saving not possible, Global Object Directory (GTADIR) request has failed.
What causes this issue? Cannot read from Global Object Directory (GTADIR). We tried to read GTADIR data for program &v1&.System Response Sav...
ESH_IEF_MSG139
Software component &1 needs package assignment
What causes this issue? Search models of the software component &V1& cannot be maintained as it does not have a package assignment.System Res...
ESH_IEF_MSG140
Status resetted: Import log and SWC model copy from 000 ('tabu-fetch')
What causes this issue? The import status of software components has been resetted.System Response How to fix this error? Procedure for System Admini...
Click on this link to search all SAP messages.