This blog belongs to a series of blogs regrouped on the SCN page “SAP PLM Recipe Development for Beginners”.
In today’s blog we take a closer look at the search capabilities in SAP PLM Recipe Development – in particular at the Advanced Search (or Enterprise Search).
In the Work Overview of your Recipe Development System, in the Quick Search Section, you can select the PLM object which you would like to search for. After having selected an object, click “Advanced Search”.
Now appears the Advanced Search screen and you can navigate through the different tabs and select and maintain various search criteria.
With the tab “Recipe Input or Output” you can for example search for all recipes which contain a certain input substance. If you want to identify all recipes which contain one of several input substances, you can also include a whole range of substances as search criteria.
The “X” on the tab “Recipe (X)” indicates, that in this tab there are also some search criteria maintained. You are thus combining various search criteria from various tabs.
If you are regularly searching for similar things, you can save the selection of maintained search criteria in a “personal query” or “global query”. Global Queries can be loaded by anyone, personal queries are only visible for you.
When you then hit the “Go-Button” or when your press “Enter”, the search hit list (a list of all objects which match with your search criteria) appears.
From the hit list, you can directly access the objects by clicking on them. You can also add them to your favorites or an object set, so you can quickly find them again later.
Another elegant way of grouping those objects is adding them to an Engineering Record.
What if you get this error?
Especially during the system implementation, you might get the following error when trying to search something “Enterprise Search Connector for object type PLM_RSPSUB is not available”.
If you do not have time to get too technical you still try to find your objects (specification or recipes) with the following temporary workaround:
In somesearch fields, you can switch from the “Enterprise Search” to the “Database Search”. The database search does not require any indexing and searches directly on the database. It is slower and there a less search fields available – but it’s good to know for workarounds.
If you want to find the root cause for your error message, you can take a look at the Enterprise Search Cockpit (transaction ESH_COCKPIT).
Here you need to know which search objects are relevant and need to be indexed. In the case of specifications, the object is “BUS1077”.
You can now schedule the re-indexing of those objects.
You can now schedule the re-indexing of those objects.
If there are some error – you can use transaction SE11 to check table TCGES01 and you will see all object which have not been indexed.
Also, it is good to know that when you change user authorizations, you need to run indexing afterwards for this object: USER_AUTHORITY.
If you don't do this, certain users might have problems finding objects with the advanced search. With SE11 you can check table ESH_AU_USR_UPD – which should always be empty. If it is not empty, it means that you have to index the USER_AUTHORITY object, as some users are probably facing search issues.
Here are some useful links:
USER_AUTHORITY – Enterprise Search
How to schedule a periodic delta index – Enterprise Search
S/4HANA Simplification Item: PLM Enterprise Search
Embedded Search for SAP Application
- SAP Managed Tags:
