Vous êtes sur la page 1sur 13

http://www.nakisa.

com

Integration and Alliances

Nakisa SAP HROCI Live


Configuration Guide

Author: Version: Date Published:

Sathish.B.Ramakrishna 1.0 July 7, 2007

Copyright Nakisa Inc. 2005. All rights reserved.


The information contained in this document represents the current view of Nakisa on the issues discussed as of the date of publication. Because Nakisa must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Nakisa, and Nakisa cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. NAKISA MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Nakisa Inc. Nakisa may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Nakisa, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. 2005 Nakisa Inc. All rights reserved. Nakisa, CDS, Corporate Directory Services are either registered trademarks or trademarks of Nakisa Inc. in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Nakisa Inc. is a leading provider of Web-based solutions for employee related information, through organization charts and telephone directory listings. Customers include Governments, Corporations, Public Utilities, Hospitals, Financial Institutions, Educational Institutions and Military.

Corporate Headquarters: 1100 Sherbrooke Street West, Suite 100 Montreal, Quebec Canada H3A 1G7 Tel.: +1 (514) 499-2823 Fax: +1 (514) 499-2824 www.nakisa.com Nakisa Inc, the Nakisa logo and CDS logo are registered trademarks of Nakisa Inc. All other company and product names may be trademarks of their respective owners. Copyright 1998-2005 Nakisa, Inc. All Rights Reserved.

Table of Contents
1 2 PREFACE.............................................................................................................................................4 HROCI 6.0 ............................................................................................................................................5 2.1 ABOUT HROCI 6.0 .............................................................................................................................5 2.2 PREREQUISITES ..................................................................................................................................5 2.3 NAMING CONVENTION ..........................................................................................................................5 EVALUATION PATHS .........................................................................................................................6 3.1 ZNAK_O2M (ORGUNIT TO ORGUNIT MANAGER) ................................................................................6 3.2 ZNAK_P2M (EMPLOYEE TO MANAGER) ..............................................................................................6 3.3 ZNAK_P2O (EMPLOYEE TO ORGUNIT HE MANAGES) ..........................................................................6 3.4 ZNAK_S2P (POSITION TO EMPLOYEE)................................................................................................7 3.5 ZNAK_O2P (ORGUNIT TO ORGUNIT PARENT+POSITIONS) .................................................................7 3.6 ZNAMOTO4 (POSITION DERIVED HIERARCHY)....................................................................................7 OBJECT SELECTION RULES ............................................................................................................8 4.1 ZNAK_OCI_RULE1 ..........................................................................................................................8 4.2 ZNAK_OCI_RULE2 ..........................................................................................................................8 4.3 ZNAK_OCI_RULE3 ..........................................................................................................................9 4.4 ZNAK_OCI_RULE4 ..........................................................................................................................9 4.5 ZNAK_OCI_RULE5 ..........................................................................................................................9 OBJECT SELECTION VIEW..............................................................................................................10 5.1 ZNAK_OCI_OSEL ..........................................................................................................................10 5.2 ZNAK_OCI_OSEL2 ........................................................................................................................10 5.3 ZNAK_OCI_OSEL3 ........................................................................................................................11 5.4 ZNAK_OCI_OSEL4 ........................................................................................................................11 ORGANIZATIONAL VIEW .................................................................................................................12 6.1 ZNAK_OCI_O2O ............................................................................................................................12 6.2 ZNAK_OCI_O2OM .........................................................................................................................12 6.3 ZNAK_OCI_O2OP..........................................................................................................................12 6.4 ZNAK_OCI_O2S ............................................................................................................................12 OTHER STANDARD OBJECTS ........................................................................................................13 7.1 STANDARD EVALUATION PATHS .........................................................................................................13 7.2 STANDARD BAPIS ............................................................................................................................13

1 Preface
This document is a configuration guide for Nakisa SAP HROCI Live, an application that extracts data directly from SAP R/3 and uses it with NOMS for a live version of SAP Organizational Chart. It is meant for Nakisa developers, consultants, customers and partners who want to use the NOMS with SAP Live connectivity. The configuration guide focuses mainly on the configurations that are needed to make the live connectivity, a crucial file that controls how data is downloaded from SAP using HROCI and used with NOMS.

2 HROCI 6.0
It is important that the following configuration must be done so that NOMS work live with SAP. NOMS uses the concepts of HROCI 6.0 and standard BAPIs in order to retrieve data from SAP. The configurations that must be done are creating the Evaluation Paths, the Object Selection Rules, Object Selection Views and the Organization Views (ORGVIEW). It is explained in detail further in this document and also be sure that names used are all similar to that in the document. It is to be noted that the there are also certain Standard Evaluation Paths that are used by the application other than the customized Evaluation Paths. The standard objects that are used, are explained later in this document.

2.1 About HROCI 6.0


The SAP HR Interface for Organizational Charting (HR-OCI) 6.0 is an interface to the SAP system for third-party vendors organizational charting applications. The interface allows a third-party vendors application to extract SAP Organizational Management objects, relationships and attribute data from SAP Organizational Management and SAP Personnel Administration. Extracted data is displayed in a graphic presentation. As HR-OCI 6.0 is a Web-enabled interface, the graphical display is mainly for the SAP Enterprise Portal and specifically for SAP Enterprise Portal roles (e. g. SAP Manager Self-Service). The interface utilizes the functionality provided by the Object and Data Provider (OADP) and SAP Query to extract the desired data from SAP Organizational Management and SAP Personnel Administration. The technical reason for SAP offering a new interface version is that the Object and Data Provider (OADP) functionality changed as of release mySAP ERP 2005. Hence, a new parameter that was introduced by the new OADP functionality needs to be reflected in the interface. This new parameter (ORGVIEW) is coming along with the organizational structure views invented in mySAP ERP 2005.

2.2 Prerequisites
Must be using mySAP ERP 2005 Support Package Stack 06. Must have deployed the Business Package for SAP Manager Self-Service (mySAP ERP) 1.0 (BP ERP05 MSS 1.0), including the changes as of mySAP ERP 2005 Support Package Stack 06 (i.e. having deployed the Organizational Chart Link, Organizational Chart Tester and Organizational Tester iViews available with this support package stack).

2.3 Naming convention


The names for the Evaluation Paths, Object Selection Rules, Object Selection View and Organizational View must be the similar the ones specified in the document (check the picture for the names). Changing the names might affect the working of the application and cause the application to break down. 5

3 Evaluation Paths
In order to use NOMS in IDES environment, certain views has to be created so that NOMS could use them to retrieve the XML and Datasets. The Steps involved in creating the Organizational views and Evaluation Paths to work with NOMS for SAP HROCI is as follows: Go to Transaction code OOAW which is maintaining evaluation paths. Create the following Evaluation Path and give the corresponding Evaluation Path Text using the New Entries in the Application Toolbar. Evaluation Paths to be created:

3.1 ZNAK_O2M (OrgUnit to OrgUnit Manager)

The evaluation path is for the Organizational unit to Organizational unit Manager, to find the Manager of an Org. unit. This is used in details panel of Organization.

3.2 ZNAK_P2M (Employee to Manager)

***Make sure the Skip is checked, for the P to S B008 hierarchy (No. 10).

The evaluation path is for the Employee to his Managers Position & Org unit. This is used to find the managers position of an employee. Then using the obtained position, the name of the manager is obtained later.

3.3 ZNAK_P2O (Employee to OrgUnit he Manages)

The above evaluation path is for the Employee to org unit he manages, if any. This is to find if the given employee is a manager or not. 6

3.4 ZNAK_S2P (Position to Employee)

The above evaluation path is for Position to Employee/Person who is holding the position. This is used in the position details panel.

3.5 ZNAK_O2P (OrgUnit to OrgUnit Parent+Positions)

The above evaluation path is for Organizational Unit to Organizational Unit Parent with the corresponding position.

3.6 ZNAMOTO4 (Position Derived Hierarchy)

The above evaluation path is used for the Position Derived Hierarchy to retrieve all the positions and corresponding persons in all the organizations. Note: Please make sure you give the Evaluation Path name as given in the figures because the application will call only those names. So make sure you enter the appropriate names.

4 Object Selection Rules


Now create the following rules for object selection. Transaction code SM34 (View/Cluster Name: VC_TWPC_OBJSELRULE). The evaluation paths that we created in the previous step will be used here as the evaluation path. Fill the input params (Evaluation Path, Depth and Function Module) with the help of the values shown in the figures given below each of the respective Rules.

4.1 ZNAK_OCI_RULE1

4.2 ZNAK_OCI_RULE2

4.3 ZNAK_OCI_RULE3

4.4 ZNAK_OCI_RULE4

4.5 ZNAK_OCI_RULE5

5 Object Selection View


Now create Object Selections View in Transaction SM31. (View Name: V_TWPC_OBJSEL). And fill the input params (Rules for Root Objects, Rules for Navigation Objects and Rule for Target Objects) with the help of the values shown in the figures given below each of the respective Object Selection Views. The Rules that we created in the previous step will be used here. Create the following Object Selection Views:

5.1 ZNAK_OCI_OSEL

5.2 ZNAK_OCI_OSEL2

10

5.3 ZNAK_OCI_OSEL3

5.4 ZNAK_OCI_OSEL4

11

6 Organizational View
Finally we have to create the Organizational View. These views have to be passed to BAPI in order to retrieve the XML string by using the HR OCI 6.0. We can create the view using the transaction code SM31 (View Name: V_TWPC_ORGVW). Create the following Organizational Views and input appropriate params given in the figures below each of the Organizational Views.

6.1 ZNAK_OCI_O2O

6.2 ZNAK_OCI_O2OM

6.3 ZNAK_OCI_O2OP

6.4 ZNAK_OCI_O2S

NOTE: Please make sure the Names must be the same in all the Views, Rules and Evaluation Paths. 12

7 Other Standard Objects


The standard objects that we have tried to use include evaluation paths and BAPIs.

7.1 Standard Evaluation Paths


The standard evaluation paths include O-O-S & O-P. In order to provide the root object the functional module HRMSS_OCI_GET_ROOT_OBJECTS is used.

7.2 Standard BAPIs


There are also some standard BAPIs that the application uses to retrieve appropriate information from SAP. The list of those BAPIs; HRMSS_GET_ORGSTRUCTURE_AS_XML HROCI RFC function call BAPI_ORGUNITEXT_DATA_GET Retrieves the information in tables given the evaluation path. Similar to HROCI function module. BAPI_EMPLOYEE_GETDATA Used for Searching and to get details of an Employee HRMSS_RFC_EP_READ_PERSONALDATA Retrieves more information for an employee like marital status and address. HRMSS_RFC_EP_READ_GENERALDATA Retrieves information about Employee, like org unit text, position text and so on. HRWPC_RFC_EP_READ_PHOTO_URI Retrieves an URL of an employee photo in SAP

13