configuring crm enterprise search sap crm 7.0

5/13/2018 Configuring Crm Enterprise Search Sap Crm 7.0 - slidepdf.com

http://slidepdf.com/reader/full/configuring-crm-enterprise-search-sap-crm-70 1/8

Configuring CRM EnterpriseSearch

SAP CRM 7.0

A D D O

N X .

N

D C

R

M

_ E S_

I N

T E G

R

A T I O

N



(C) SAP AG ADDONX.NDCRM_ES_INTEGRATION 2

Copyright

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM,z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower,PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect,RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere,Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World WideWeb Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessByDesign, and other SAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are the trademarks of

their respective companies. Data contained in this document serves informational purposes only.National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AGand its affiliated companies ("SAP Group") for informational purposes only, without representationor warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect tothe materials. The only warranties for SAP Group products and services are those that are setforth in the express warranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional warranty.




Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identifydifferent types of information at a glance. For more information, see Help on Help

General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library .

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and tabletitles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.




1. Connecting a CRM System to Enterprise Search ......................................52. Initial Extraction..........................................................................................63. Delta Extraction..........................................................................................64. Technical Monitoring ..................................................................................7




Configuring CRM Enterprise Search

You can use this document for your day-to-day work with Enterprise Search (ABAP)within SAP CRM. It is focused on CRM templates delivered by SAP.

1. Connecting a CRM System to Enterprise Search

You can connect a CRM system to Enterprise Search (ABAP) in Customizing for

Customer Relationship Management at UI Framework -> Enterprise Search Integration.

Note

If only search enablement is required, only steps 1 and 2 are necessary. If, on the otherhand, templates are to be modeled as well, all four steps need to be performed.

1. Define TREX Connection for Enterprise Search

If the connection has already been created, you simply specify it in Customizingfor Customer Relationship Management at UI Framework -> Enterprise Search

Integration -> Define RFC Destination for TREX .

If the connection does not yet exist, you have to log on to the TREXAdministration UI and proceed as follows:

1. Create a connection to your backend system

Specify the system name, system number, application server, defaultclient, TREX user, and password.

2. Create an RFC destination to your backend systemSpecify the RFC destination name.

2. Define Parameters for Initial Extraction

You define parameters for initial extraction in Customizing for Customer

Relationship Management at UI Framework -> Enterprise Search Integration -> Define Settings for Parallel Extraction.

3. Specify Client for Template Modeling

You specify the client for template modeling in Customizing for Customer

Relationship Management at UI Framework -> Enterprise Search Integration ->Specify Client for Template Modeling.

4. Specify Software Component for Template Transfer

You specify the software component for the template transfer in Customizing forCustomer Relationship Management at UI Framework -> Enterprise Search

Integration -> Specify Software Component for Template Transfer .




2. Initial Extraction

After you have configured the CRM system for Enterprise Search, the data has to be

extracted to Enterprise Search. You have the following options:

1. Extracting Data of All Templates

This is only feasible if the data volume is small. Nevertheless, it can take severalhours until all data is extracted. For this purpose, execute program

ESH_ADM_INDEX_ALL_SC in the background. Specify variant ES_INDEX_RUN withthe following parameters:

Parameter Value

Delete All Search Connectors X

Create All Search Connections X

Product BBPCRM

Schedule Initial Indexing X

The job creates a separate extraction job for every template. If initial extraction

takes longer than a day to complete, you should consider scheduling initialextraction for each template separately (see below).

Note

If no connector has been created beforehand, the job is not successfully executed.For more information, see SAP Note 1278561.

2. Extracting Data of a Specific Template

Log on to the Enterprise Search Administration Cockpit of the CRM system. It is

available in SAP Easy Access Menu for Customer Relationship Management at

Architecture and Technology -> Enterprise Search Integration -> Tools -> ES

Administration Cockpit . Alternatively, you can call transaction ESH_COCKPIT.

You need authorization SAP_ESH_LOCAL_ADMIN. Proceed as follows:

1. Select the template to be extracted

2. Choose Actions -> Schedule Indexing

3. Delta Extraction

After initial extraction is completed, delta extraction has to be scheduled so that changesto CRM objects are reflected in Enterprise Search.




Caution

We do not recommend scheduling delta indexing for all CRM templates from the ES

Administration Cockpit, as every template is processed in a separate background process.The reason is that batch processes may become completely blocked by Enterprise Search

processes. Instead, program ESH_IX_PROCESS_CHANGE_POINTS should be used. It

processes all templates in one logical unit of work (LUW) and thus occupies only onebatch process.

Create a variant with an appropriate name, for example, RUN_EVERY_MIN, or

RUN_EVERY_5MIN, reflecting the period of delta extraction. For variant RUN_EVERY_MIN,specify the following parameters:

Parameter Value

Product BBPCRM

Delay [seconds] 60

Exit processing after [hours] 24

Reschedule automatically X

Process in background X

P_RESTX X

4. Technical Monitoring

For the technical monitoring you need to perform the following checks:

1. Check Enterprise Search Cockpit

Log on to the Enterprise Search Administration and check if all connectors are

active. Specifically, check that no connectors have status “ Error”. If errorsoccurred, click tab Job Log for more details.

2. Check for Short Dumps

Log on to the CRM system and call transaction ST22. Check if there are any short

dumps related to Enterprise Search.

3. Check Delta Indexing Job

Check status of job ESH_IX_PROCESS_CHANGE_POINTERS in transaction SM37.

Check the application log for delta indexing under object CRM_ES and subobject

CRM_ES_DELTA_EXTR.

4. Check Initial Indexing Jobs




The job ESH_ADM_INDEX_ALL_SC spans as many separate jobs as there are

templates. Check the application log under object CRM_ES and subobject

CRM_ES_DATA_EXTR.

Each job executes program ESH_IX_CRT_INDEX_OBJECT_TYPE with a variant that

holds the execution parameters. Among others, the template ID is saved. To view

them, call transaction SE38 and start program ESH_IX_CRT_INDEX_OBJECT_TYPE,select Variants, and specify the variant number from the job log.

Caution

Even if the initial indexing is flagged as successful, there could still have been

dumps generated. Therefore, it is important that you scan for errors in the dumpdatabase.

Note

If you encounter exception CX_ESH_IF_NOT_SUPPORTED, regarding one order

authorization templates such as CRM_ACE2_BP_UCT, CRM_ACE2_LC_UCT,CRM_ACE2_LC_AC, CRM_ACE2_PR_UCT, CRM_ACE2_BP_ACL, CRM_ACE2_PR_ACL,

CRM_ACE2_OO_ACL, CRM_ACE2_OO_UCT, or CRM_ACE_USER_OTS, you may have toactivate the corresponding BAdI extraction (definition

BADI_ESH_IF_OBJECT_DATA, implementation CRM_ESH_1O_AUTHORITY)manually.

More Information

Enterprise Search Integration

configuring crm enterprise search sap crm 7.0

Documents