Task:
We want to use additonal fields in the enterprise search for contact persons and we have CRM 7.0 EHP1.
Step 1: Create new template set.
Use the same component set as teh original, e.g. BP_APPL for contact persons.
Transaction CRM_ES_WB.
Step 2: Copy template CRM_CONTACT in this newly created template set.
The target template ID has to start with Z.
Step 3: Adjust “Search”, “Result” and “Select”-Flags for the attributes
Step 4: Transfer templates
We used BBPCRM.
Step 5: Configure extraction user for indexing.
We used DDIC.
Step 6: Create new search object connector
Transaction ESH_COCKPIT.
Step 7: Schedule indexing
Delete previous content.
Step 8: If errors happend, start indexing in GUI.
Report ESH_IX_CRT_INDEX_OBJECT_TYPE.
Step 9: Test connector
Program ESH_TEST_SEARCH.
The new atttributes should be available now.
Step 10: Set namespace /1CRMES/ as changeable
Step 11: Create search-query-structures
Report CRM_ES_STRUC_GEN
Step 12: Test query in BOL-browser
Transaction: GENIL_BOL_BROWSER
Step 13: Add new query in customizing for enterprise search
SPRO: CRM – UI Framework – Technical Role Definition – Define Central Search
Step 14: Clear cache of central search
Class CL_CRM_CENTRAL_SEARCH
Execute method CLEAR_CACHE
Finished.
Good luck when implementing.
Thomas Wagner
Do you know if the CRM_ES_STRUC_GEN report is still required in EHP3 SP06?
I would like to add to the result view the custom attribute I added in the modeler. In my case, the corresponding GenIL object is CRM_ACCOUNT_ESResult. I therefore think I have to modify it if I want my attribute to be displayed in the result view.
So I ran CRM_ES_STRUC_GEN with the following parameters:
But at the end, it asks me for an access key, as it tries to modify the standard /1CRMES/CRM_ACCOUNT_R structure. I don't want to provide the access key unless I'm sure that is the good thing to do.
Hello Mathieu,
EHP6? I thought the latest one was CRM 7.0 EHP3.
I never did it with EHP3 or 6 but I can remember that I (or the customer I was working for) had to register the standard search structure with EHP1. We never had a problem with that.
Best regards,
Thomas
But wait, I remember it very vaguely only. Did you set the namespace /1CRMES/ as modifiable as I have written it? Maybe that should do it.
Thank you for your reply.
I didn't have to do it: it was already modifiable.
I can't remember if this setting was enough or if I still had to register the object. But even registering it should not hurt you.
Thomas
OK, I think I will give it a try.
Thank you for your help.
Oops sorry, EHP3 SP06!