Do you have any question about this error?
Message type: E = Error
Message class: ESH_TAU_MSG - Test Automation
Message number: 035
Message text: Realtime indexing for EPM purchase order (methods: traditional and push)
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Enterprise Search supports two modes of realtime indexing:
Traditional (only change pointers)
Push (change pointers AND connector data)
For demo and test purposes, Enterprise Search offers two software
components:
EPM Demo: ESH_EPM_DEMO/Z_ESH_EPM_DEMO -> "Traditional" realtime indexing
EPM Auto: ESH_EPM_AUTO/Z_ESH_EPM_AUTO -> "Push" realtime indexing
The listener for realtime indexing is triggered by changes of the EPM
purchase order, especially (i.e. header note). The implementation is
located in class CL_EPM_ES_LISTENER, method ON_AFTER_SAVE.
Additional info on how to change a EPM purchase order:
Launch transaction ESH_SEARCH (Search-UI, Web Dynpro)
Display any EPM purchase order
Click the title of the purchase order to launch the application "PO
Maintenance Application" (Web Dynpro, s_epm_wd_po). If the title is not
enabled (not a hyperlink), activate UI-Technology "Web Dynpro", using
Connector Administration Cockpit (ESH_COCKPIT), menu System Settings->
Maintain UI Technologies.
Add a note or change an existing note. Save the PO to trigger realtime
indexing.
Additional info for alternative RTI demo/testing
Report ESH_TST_RTI_ERROR_HANDLING creates change pointers and can also
simulate issues to validate error handling. Moreover periodic creation
of change pointers is supported.
Error message extract from SAP system. Copyright SAP SE.
ESH_TAU_MSG035
- Realtime indexing for EPM purchase order (methods: traditional and push) ?The SAP error message ESH_TAU_MSG035 typically relates to issues encountered during the real-time indexing process for Enterprise Performance Management (EPM) purchase orders. This error can occur when the system is unable to index the data correctly due to various reasons. Below are some common causes, potential solutions, and related information for this error:
Causes:
- Data Inconsistencies: There may be inconsistencies or missing data in the purchase order that prevent successful indexing.
- Configuration Issues: Incorrect configuration settings in the EPM or the underlying SAP system can lead to indexing failures.
- System Performance: High system load or performance issues can cause timeouts or failures during the indexing process.
- Authorization Issues: The user or process attempting to perform the indexing may lack the necessary authorizations.
- Technical Errors: Bugs or technical issues in the SAP system or the EPM module can also lead to this error.
Solutions:
- Check Data Integrity: Verify that the purchase order data is complete and consistent. Look for any missing fields or incorrect values.
- Review Configuration: Ensure that the EPM and indexing configurations are set up correctly. This includes checking the settings for real-time indexing.
- Monitor System Performance: Check the system performance metrics to see if there are any bottlenecks. If the system is under heavy load, consider scheduling indexing during off-peak hours.
- Authorization Check: Ensure that the user or process has the necessary authorizations to perform the indexing. You may need to consult with your SAP security team.
- Check Logs: Review the application logs and system logs for any additional error messages or warnings that could provide more context about the failure.
- Update SAP: Ensure that your SAP system is up to date with the latest patches and updates, as these may contain fixes for known issues.
- Contact SAP Support: If the issue persists, consider reaching out to SAP support for assistance. Provide them with detailed information about the error and the context in which it occurs.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
ESH_TAU_MSG033
Creation of ranking parameters has failed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_TAU_MSG032
Creation of ranking factors has failed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
ESH_TAU_MSG036
EPM software component &1 does not exist.
What causes this issue? The EPM software component &V1& does not exist.System Response You currently cannot use software component &V1&a...
ESH_TAU_MSG037
Enterprise Search is not configured (EPM SWC import not posssible)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.