Enterprise Search in SAP CRM EHP3 7.0

[sensap23]

The following document is regarding Enterprise search functionality for Trex concentrating on deletion and creation of connectors for All account,contacts and employee and finally carrying out indexing let us start doing this in step by step process to get to know more in detail.

Step By step Process :

1.STC01 - Delete and create connectors and run a report to SAP_ESH_CREATE_INDEX_SC

2.ESH_COCKPIT - Indexing the connectors for account,contacts and employee

1.STC01 - Delete and create connectors and run a report to SAP_ESH_CREATE_INDEX_SC :

STC01 Transaction code is used for deletion and creation of connectors for All account,contacts and employees.Here previously we used to run a report ESH_ADM_INDEX_ALL_SC till SAP CRM EHP1 7.0 version which has become obsolete now and currently in SAP CRM EHP3 7.0 it is SAP_ESH_CREATE_INDEX_SC replaced.

Go to Tcode STC01 give SAP_ESH_CREATE_INDEX_SC for Task List and click on execute system will ask to maintain task list parameters here need to make sure to tick mark under execute section for following task description except for e option below remaining needs to selected.

a.Check if the Client is Configured

b.Delete Connectors

c.Select Software Component and Included Models

d.Create and Index Connectors

e.Set Parameters for Consolidating Connector Status

f.Consolidate Connector Status

In the option c "Select Software Component and Included Models" we have to maintain under fill parameters select software component as BBPCRM and select models manually here need to select object type CRM_ACCOUNT,CRM_CONTACT and CRM_EMPLOYEE as a variant and click execute.

It will ask for back ground execution of job and make sure the job runs successfully in SM37.

2.ESH_COCKPIT - Indexing the connectors for account,contacts and employee :

On successful completion of job in ESH_COCKPIT we can able to see connectors for account,contact and employee gets created after deletion and the status will keep changing from scheduled for indexing ,prepared and finally active.

After that we need to maintain the settings as follows  ACCOUNT- ACTIONS- SCHEDULE INDEXING- START DATE IMMEDIATELY- REAL TIME INDEXING, SELECT ALL, COPY SETTINGS and clicked OK

Note : We need to implement correction from SAP NOTE 2051372 to over come the above mentioned error "Exception at 'JOB_SUBMIT': INVALID_JOBDATA"

Happy Learning!!!