Error Handling During Searches
In Customizing for the search engine service, check whether the service is correctly configured. Choose SAP NetWeaver ® SAP Web Application Server ® System Administration ® Search Engine Service ® System Settings.
Check whether the TREX system is accessible. Perform the following availability test:
...
1. Start transaction SES_ADMIN.
2. Choose TREX Admin ® RFC Administration ® Connection Test.
If the system displays the error message No RFC connection when you perform the test, this means that the TREX system is not accessible. In this case, check whether the RFC destination data is correct (transaction SM59). For more information about setting up an RFC connection, see the SAP NetWeaver 7.0 Search and Classification (TREX) installation guide.
The delta indexing method for your business object type works with change pointers and a periodic delta indexing job. This means that unlike with the quick, direct indexing method you can only find created or changed objects once the indexing job has run.
Check whether or not the job has run successfully after the object was created or changed. In addition, you can trigger delta indexing directly by opening transaction SES_ADMIN and choosing Index Immediately ® Delta.
To ensure that search results are always up-to-date, reduce the amount of time between jobs or implement/activate the quick, direct method of delta indexing.
More information: Scheduling Periodic Indexing.
See the previous section.
You can only find attributes that already existed for the objects but were not previously added to the TREX index after the next time the TREX system performs a complete indexing run.
You must perform a complete indexing run (not delta indexing) because this is not a change to the objects concerned and therefore no change pointer is written to the change pointer table. This means that this change cannot be added during delta indexing. You must therefore perform a complete indexing run.
To perform a complete indexing run, start transaction SES_ADMIN.