Talent management esh - extend search model how to v1.2

Enterprise Search ModelExtensions in

Talent Management

SAP ERP 6.0 Enhancement Pack 4

SAP Help 20 January 2010

Talent Management Enterprise Search Extension 2

Copyright

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without prior notice.

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

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli,Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks ofIBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks ofAdobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademarkof 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 are trademarks orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, 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 for technology inventedand implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentionedare the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The onlywarranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.



1 Introduction

1.1 Scope of this document

This document describes how to extend business model of enterprise search for Talent Managementfor PA and PD Infotype Data as of release ERP 2006. The goal is to provide standards how to makeadditional infotype data searchable, so that it can be used in existing applications of Talent

Management.

This document does also describe how an existing application can integrate new search fields wherealready other are used.

1.2 Overview: HCM Data Model in Enterprise Search Modeling



The Enterprise Search Modeling forTalent Mangement consists of several Enterprise Search BusinessTemplates. Each object type (e.g. central person CP, person P, Position S …) is represented by onetemplate. The root nodes of these templates represent Inftype 1000 data. Further nodes of thesetemplates represent other Infotypes for the object type e.g. in the templateHRTMC_CENTRALPERSON the node Education holds data of Infotype 7404.For each relation (Infotype 1001 data) between these object types which is relevant for the search(e.g. relation 209 between CP and P) a special template is created. These relation templates are usedto link the templates which represent object types so that in the search for objects from onetemplate like HRTMC_CENTRALPERSON attributes from other templates like HRTMC_PERSON can beused as search criteria.

If attributes of Infotypes or object types which are not yet existing in the Enterprise Search Modelingare needed as search criteria the task is to extend the Enterprise Search Modeling. This is possible byeither create new templates or extend existing templates by new nodes.



1.3 Enterprise Search Model Changes in Customizing Client

Any Customer Changes on already delivered Search Model should be done in Customizing Client todo those changes transportable.

If the Extensions are done in the different client, then use the ‘Client Copy’ functionality fromAdministration Cockpit.

This feature is very helpful to create Backups from the software components you are working on.



2 Model and Back End Extensions for PA infotype data

In this chapter will be described an example how to extend existing Enterprise Search Model tosearch for persons who are in special Pay Scale Group. This data is stored in PA Infotype 0008 (BasicPay), field TRFGR.

Important: log on in to the system and do all changes in customizing client!

1. Start the Enterprise Search Administration Cockpit and switch to Modeler

2. Create new own Software ComponentSoftware Component -> define Software Components

Create -> New Software Component ‚Z_COMPNAME‘ (don’t use any other selection fields)



3. Include EA-HRGXX Software Component

Select already new created software component and include the EA_HRGXX

4. Create new Node in HRTMC_PERSON Template

All data related to the Person (not Central Person) and based on personal number (not on

CP) is collected in the business template HRTMC_PERSON. Select this Template within ofnew created component to be extended (e.g. Z_DIMI -> EA_HRGXX->HRTMC_PERSON) andclick on edit button. On ‘Define Nodes’ step click on ‘Create Node’-Button and enter newnode name ‘BASIC_PAY_DIMI’, node description and data source (Infotype table PA0008).

5. Select related attributes of new NodeSelect new created Node ‘BASIC_PAY_DIMI’. In the second table you can select neededattributes, mark it as Response Attributes, add some key fields if needed (all key fields areowned from the DDIC table PA0008). Very important is to add semantic information to suchan attributes like ENDDA, BEGDA or LANGU.



6. Create Composition to Parent Node ‘OBJID’Select Parent Node ‘OBJID’ and create composition to the new node ‘BASIC_PAY_DIMI’.

7. Define foreign Keys of child Node

In step ‘Define Structure’ select node BASIC_PAY_DIMI and in the second table create foreignKey between Parent Node ‘OBJID’ and Child Node ‘BASIC_PAY_DIMI’ based on personal

number.

8. Save Template ‚HRTMC_PERSON‘

9. Change Search Request of ‘HRTMC_CENTRAL_PERSON’Due the current search model is based on Central Person ID and not on Personal ID therelation CP<->P is needed. The business template for this relation is already available and iscalled HRTMC_REL_CP_P_209. Additionally the Template ‘HRTMC_CENTRAL_PERSON’ needsto be changed in the model to make search for Pay Scale Groupe possible.Select the Template and click on ‘Edit’ and go to the step ‘Define Requests’. Select SearchRequest ‘SAP_TALENT’ due we want to change Extended Search for Talents in this example

and click on ‘Add’ in the table of attributes of request.



Select the request attributes in according with designed model:HRTMC_CENTRAL_PERSON->HRTMC_REL_CP_P->HRTMC_PERSON->BASIC_PAY_DIMI



10. Save business template ‘HRTMC_CENTRAL_PERSON’

11. Customizing for ‘Define Search Models and Change Pointers’

Go to Customizing point ‘Define Search Models…’ of Talent Management and display nodesof template ‘HRTMC_PERSON’.

Add Node ‘BASIC_PAY_DIMI’ with Extraction Class ‘CL_HRTMC_SEARCH_READ_PA_INFTY’ forInfotype 0008 and field name PERNR. Add also information to the change pointer control(Infotype 0001; Infotype 1001, Object type P, relation A209). Save this data.



12. Customizing for UI field

Start customizing for Search Requests and Search Field Names. Select templateHRTMC_CENTRALPERSON and search request name SAP_TALENT and click on Search Fields.Add new search field with name for example S_BASIC_PAY_DIMI_TARIF_GRP. Fill additionalinformation like alias of reference field in the search model (it is displayed via searchcockpit), reference table, reference field, node name and Infotype. Check boxes for F4 Helpand DDIC are needed for the case the text values are in Dictionary available and could beused for F4 Help or Drop Down list box.

In addition to a new created field the definition of search configuration should be done. It isalso possible to create a new UI search field group.Start customizing step ‘Define Search Configurations’ and select search configuration ‘SAPTALENT’. Using step ‘Search Field Groups’ define new UI Group ‘S_GROUP_9’ withdescription.

Switch to Search Fields and mark field S_BASIC_PAY_DIMI_TARIF_GRP as search field, addfield group name if needed and position within this group.



13. Recreate search connectors and start indexing

Start the Search Cockpit and delete all existing search connectors. Create new connectorsusing templates from new software component Z_DIMI. Start Indexing for all connectors.

Or use the program ESH_ADM_INDEX_ALL_SC for the software component Z_DIMI.

After successfully indexing check the number of physical indices via search cockpit:



14. Test new Searchable objects

At the End test you application searching for Pay Scale Group or use the programESH_TEST_SEARCH to execute attribute search.



3 Model and Back End Extensions for PD Infotype data

This chapter describes how to make new data from PD Infotypes searchable.

1. Changes in the Enterprise Search ModelThe steps are similar to extension for PA objects as described in the chapter before. The newnode should be created in the search template HRTMC_CENTRALPERSON due most of PDobjects are based on Central Person ID und could be searchable via Central Person Objectdirectly.

The relation CP<->P is even not needed – structure of HRTMC_CENTRALPERSON can becompleted directly via Composition and the response attribute can be added without usingthis relation.

Important: log on in to the system and do all changes in customizing client!

a. Start the Enterprise Search Administration Cockpit and switch to Modelerb. Create new own Software Componentc. Include EA-HRGXX Software Componentd. Create new Node in Template ‘HRTMC_CENTRALPERSON’e. Select related attributes of new Nodef. Create Composition to parent Node ‘OBJID’g. Define foreign Keys of child Nodeh. Change Search Request of ‘HRTMC_CENTRALPERSON’i. Save business template ‘HRTMC_CENTRAL_PERSON’

2. Customizing for ‘Define Search Models and Change Pointers’ and Customizing for UI fieldThe customizing is similar to extensions for PA search field.

3. Recreate search connectors and start indexingStart the Search Cockpit and delete all existing search connectors. Create new connectorsusing templates from new software component Z_DIMI. Start Indexing for all connectors.


After successfully indexing check the number of physical indices via search cockpit

4. Test new Searchable objectsAt the End test you application searching for Pay Scale Group or use the programESH_TEST_SEARCH to execute attribute search.



4 Model and Back End Extensions for own objects

In this chapter will be described how to make own objects searchable. For Example we want tosearch for persons who has visited training ‘xyz…’. The Training has an object type ‘E’ and neededtraining name is saved as STEXT in HRP1000 table. The training name is language dependent. There isa relation between the object Training and the person. Therefore we need 2 new business objects inthe search model: MY_RELATION_P_E_023 and MY_TRAINING.

1. Start the Enterprise Search Administration Cockpit and switch to Modeler

2. Create new own Software ComponentSoftware Component -> define Software Components

Create -> New Software Component ‚Z_COMPNAME‘ (don’t use any other selection fields)



3. Include EA-HRGXX Software Component

Select already new created software component and include the EA_HRGXX

4. Create new business object

As template the object ‘HRTMC_JOB_FAMILY’ could be taken due to similar structure. Selectthe software component EA_HRGXX under Z_DIMI and click on create button. Enter templatename and description.

Edit new created object and add Nodes ‘OBJID’ with data source HRP1000 (Attributes: OBJIDas response field, PLVAR and OTYPE) and TRAINING_NAME also with data source HRP1000(Attributes: OBJID as resp. field, BEGDA, ENDDA, LANGU, SEQNR, STEXT as resp. field). Markalso the semantics for BEGDA, ENDDA and LANGU fields and ‘Contains text’ for STEXTAttribute.



Create Composition OBJID-TRAINING_NAME on ‘Define Structure’ Step. The foreign keyrelation will be created due to the name equality automatically.

Define response attributes forNode OBJID:

OBJID-OBJIDOBJID->TRAINING_NAME-STEXT

Node TRAINING_NAME:TRAINING_NAME-OBJIDTRAINING_NAME-STEXT.

At the end create the default request with one attribute OBJID.



5. Create new Relation from Person to Training object

As template the relation ‘HRTMC_REL_S_JF_450’ can be used. Create a new business object‘MY_REL_P_E_023’ and add new node REL_P_E_023 with Data SourceHRTMC_S_SEARCH_RELATION.

Define Structure for new relation creating association to objects MY_TRAINING.OBJID withforeign key (SCLAS<->OTYPE and SOBID<->OTYPE) and HRTMC_PERSON (OBJID<->OBJID).

At the end create and DEFAULT search request with attributes BEGDA, ENDDA, OBJID andSOBID. Save new created template.



6. Adding additional Request Field

The template ‘HRTMC_CENTRAL_PERSON’ needs to be changed in the model to make searchfor Training Name possible adding new request attribute in request ‘SAP_TALENT’ due thecurrent search model is based on Central Person.

The relations CP<->P (HRTMC_REL_CP_P_209) and the new created relation P<->E(MY_REL_P_E_023) will be used to reach the attribute TRAINING_NAME. Select the Templateand click on ‘Edit’ and go to the step ‘Define Requests’. Select Search Request ‘SAP_TALENT’and click on ‘Add’ in the table of attributes of request. Save template.

Attribute Reference:OBJID(REL_CP_P)->HRTMC_REL_CP_P_209.REL_CP_P(REL_CP)->HRTMC_PERSON.OBJID(REL_E_P)->MY_REL_P_E_023.REL_P_E_023(REL_P)->MY_TRAINING.OBJID->MY_TRAINING.TRAINING_NAME

7. Define Search Models and Change Pointers

Use customizing point ‘Define Search Models and Change Pointers’ to provide new Templatenames MY_REL_P_E_023 and MY_TRAINING.



8. Create BAdI implementation for new objects

To activate extraction for new objects new BAdi implementation with correct filter values isneed. Use transaction SE19 (BAdI Builder) and create implementation for Enhancement SpotBADI_ESH_IF_OBJECT_DATA using Implementation class CL_HRTMC_SEARCH_EXTR_OBJECTSwith BAdI definition BADI_ESH_IF_OBJECT_DATA for business objects and classCL_HRTMC_SEARCH_EXTR_RELATIONS with BAdI definition BADI_ESH_IF_OBJECT_DATA forRelations.

Set template name of object in one case or of relation in other case as filter value for currentenhancement implementation and activate it at the end.

9. Customizing for Search UI fields and recreation of connectors

Do additional setting for Search UI fields as already described in chapter ‘Customizing for UIfield’ before. Recreate all connectors using Software Component Z_DIMI and start indexing(see chapter ‘Recreate search connectors and start indexing’).






After successfully indexing check the number of physical indices via search cockpit-

11. Test new searchable objects




5 Enterprise Search and Customer Includes

In this chapter will be described an example how to extend existing Enterprise Search Model forCustomer Includes. For example Infotype 7406 (Mobility) with new fields Z_MY_FIRST_COMP andZ_MY_SECOND_COMP, which will be a attribute of business object HRTMC_CENTRALPERSON inTalent Management Model.

1. Create Customer Include in the Structure HRP7406 (Mobility)

Create new structure CI_7406 with example components Z_MY_FIRST_COMP andZ_MY_SECOND_COMP and activate it.

2. Create new Software Component

Start the Search Administration Cockpit in customizing client, switch to modeler and createnew Software Component as already described in the chapter ‘Create new own SoftwareComponent’ and ‘Include EA-HRGXX Software Component’.

3. Add new attributes to the Node

Select Template HRTMC_CENTRALPERSON from new created Software Component and on‘Define Nodes’ step select Node ‘Mobility’. Select new Attributes Z_MY_FIRST_COMP andZ_MY_SECOND_COMP from the structure and mark it also as response attributes.



4. Define new request fields

Switch to the step ‘Define request fields’, select request ‘SAP_TALENT’ and add requestattributes for new structure fields Z_MY_FIRST_COMP and Z_MY_SECOND_COMP.

5. No changes in customizing for extraction

Due to dynamic extraction no changes in customizing settings for extraction are needed.

6. Customizing for new Search UI fields

Create new search UI fields using Customizing for Search as already described in chapters‘Customizing for UI field’.






After successfully indexing check the number of physical indices via search cockpit-

8. Test new searchable objects
