Professional Documents
Culture Documents
How To Create Employee Hierarchy Extractor - CRM BW PDF
How To Create Employee Hierarchy Extractor - CRM BW PDF
Applies to:
This paper and the programs are checked on ECC 5 or higher (640 or 700) with plug-in PI 2005_1 (for
640 or 700).
Summary
In the BW Business Content, theres no DataSource available for providing a hierarchical structure for an
employee. In typical cases, in BW managers want to have access to their subordinate employees and/or
the data they are responsible for/authorized to. This paper will show you how to create a Hierarchy
DataSource for an employee object.
Author(s): Luc Boodts (luc.boodts@sap.com)
Company: SAP Belgium
Created on: October 2007
Author Bio
Luc Boodts has been working for SAP Belgium for 9 years, currently in the position of
Principal Consultant NetWeaver BI. He has over 8 years of experience in the SAP HR
domain in various modules. For SAP he has been working in the areas of HR, BW and EP
and has good ABAP knowledge.
Table of Contents
Business Scenario ........................................................................................................................................ 3
Introduction................................................................................................................................................ 3
Limitations ................................................................................................................................................. 3
Step by step description................................................................................................................................ 4
Create Function Group .............................................................................................................................. 4
Create Function Module for Data Extractor............................................................................................... 4
Global Data Definition................................................................................................................................ 6
Create Subroutines in Subprograms-Include Program ............................................................................. 8
Create Function Module for Hierarchy Catalog ....................................................................................... 12
Customizing in Source System ............................................................................................................... 14
Create the BW Datasource in the Source System .................................................................................. 15
Create the Corresponding InfoObject in BW ........................................................................................... 16
Create an InfoPackage to Test/Load Data .............................................................................................. 17
Appendix DataSource Creation Program................................................................................................. 21
Copyright ..................................................................................................................................................... 24
Business Scenario
You need to be able to grant access to grant managers access to the data their subordinates are
responsible for. Theres no standard BI Content to provide you with an employee hierarchy. Theres a
hierarchy provided in the BI Content for Organizational Unit, but this does not really suit, since you want
the manager of the org.unit to be able to see the data, without using organization unit.
With the hierarchy on an employee object, you can grant managers access through the authorizations
based on a hierarchy. This hierarchy will contain their personnel number, which you can then pre-fill with
an exit-variable in the authorizations (RSECADMIN).
Possible scenarios are : give access to managers for cost centers for which their subordinates are
responsible, profit centers, administrator groups in HR, projects,
Introduction
The extractor/DataSource described hereafter is based on the Organization Unit Hierarchy DataSource,
and uses a similar process to extract the data. It makes use of SAP ERP standard function modules for
Human Resources.
In appendix a coding sample is provided, to make the necessary table updates for your hierarchy
extractor to work.
Limitations
This document only describes how to set up the hierarchy extractor and not the authorization setup.
The extractor only allows having 1 manager for an organizational unit at one point in time, and one
employee can only belong to one organizational unit. This is because of the limitations of a BW Hierarchy
(one object can only occur once at one point in time). The extractor extracts the data on system date and
does not include time dependency.
FUNCTION Z_BW_EMPL_HIERARCHY_TRANSFER.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(I_S_HIEBAS) TYPE RSAP_S_HIEBAS
*" VALUE(I_S_HIEFLAG) TYPE RSAP_S_HIEFLAG
*" VALUE(I_S_HIERSEL) TYPE RSAP_S_HIER_LIST
*" TABLES
*" I_T_LANGU TYPE SBIWA_T_LANGU
*" E_T_HIETEXT TYPE RSAP_T_HIETEXT
*" E_T_HIENODE TYPE RSAP_T_HIENODE
*" E_T_FOLDERT TYPE RSAP_T_FOLDERT OPTIONAL
*" E_T_HIEINTV TYPE RSAP_T_HIEINTV OPTIONAL
*" EXCEPTIONS
*" INVALID_CHABASNM_HCLASS
*" INVALID_HIERARCHY_FLAG
*" INVALID_HIERARCHY_SELECT
*" LANGU_NOT_SUPPORTED
*" HIERARCHY_TAB_NOT_FOUND
*" APPLICATION_ERROR
*"----------------------------------------------------------------------
* build hierarchy
PERFORM FILL_STRUCTURES TABLES LOC_HIENODE
LOC_HIETEXT
USING I_S_HIEBAS-CHABASNM
I_S_HIERSEL
CHANGING SUBRC.
IF SUBRC = 0.
APPEND LINES OF LOC_HIENODE TO E_T_HIENODE.
* description of hierarchy
PERFORM FILL_HIETEXT TABLES LOC_HIETEXT
I_T_LANGU
USING I_S_HIEBAS-CHABASNM
I_S_HIEBAS-HCLASS
I_S_HIERSEL
CHANGING SUBRC.
IF SUBRC = 0.
APPEND LINES OF LOC_HIETEXT TO E_T_HIETEXT.
** description of virtual root = description of hierarchy
* LOOP AT LOC_HIETEXT.
* MOVE-CORRESPONDING LOC_HIETEXT TO E_T_FOLDERT.
* E_T_FOLDERT-IOBJNM = '0HIER_NODE'.
* E_T_FOLDERT-NODENAME = 'ROOT'.
* APPEND E_T_FOLDERT.
* ENDLOOP.
ENDIF.
else.
raise hierarchy_tab_not_found.
ENDIF.
ENDFUNCTION.
INCLUDE RHODAT00.
* Sonstige type
TYPES: RHIE_SUBRC LIKE SY-SUBRC.
TYPES: RHIE_FORMNAME LIKE TFDIR-FUNCNAME.
* Dates
DATA LOWDATE LIKE PLOG-ENDDA VALUE '19000101'.
DATA HIGHDATE LIKE PLOG-ENDDA VALUE '99991231'.
tables : hrp1000.
Create subroutine collection by editing the program LZBW_EMPL_HIERARCHYF01 and enter the source
code below.
Source code
*----------------------------------------------------------------------*
* INCLUDE LZBW_EMPL_HIERARCHYF01 *
*----------------------------------------------------------------------*
*---------------------------------------------------------------------*
* FORM FILL_STRUCTURES *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
* --> HIENODE *
* --> HIETEXT *
* --> VALUE(I_CHABASNM) *
* --> VALUE(I_HIENM) *
* --> VALUE(I_VERSION) *
* --> VALUE(I_HCLASS) *
* --> VALUE(I_S_TIMEINT) *
* --> SUBRC *
*---------------------------------------------------------------------*
t_orgman type hashed table of x_orgman with unique key orgunit," person,
w_manag type x_manag,
w_person like hrp1001,
w_orgman type x_orgman,
w_manag2 type x_manag2,
w_hier type struc,
w_hier3 type shorthier,
c_hier3 type shorthier,
w_hiepers like hrp1001-objid.
if sy-subrc ne 0.
endif.
****************
loop at t_manag into w_manag.
w_manag2-sobid = w_manag-sobid.
w_manag2-sobid2 = w_manag-sobid2.
insert w_manag2 into table t_manag2.
endloop.
if sy-subrc ne 0.
endif.
t_persons2[] = t_persons[].
loop at t_persons transporting no fields
where objid = '53008773'
and sobid = '00044568'.
delete t_persons.
endloop.
delete adjacent duplicates from t_persons comparing objid.
t_person[] = t_persons[].
if t_persons2[] ne t_persons[].
CALL FUNCTION 'RSAL_LOG_WRITE'
EXPORTING
I_MSGTY = 'W'
I_MSGID = 'RJ'
I_MSGNO = '053'
I_MSGV1 = 'Duplicate managers found'
I_MSGV2 = ''.
endif.
Source code
FUNCTION Z_BW_EMPL_HIERARCHY_CATALOG.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(I_S_HIEBAS) TYPE RSAP_S_HIEBAS
*" VALUE(I_S_HIEFLAG) TYPE RSAP_S_HIEFLAG
*" VALUE(I_S_HIERSEL) TYPE RSAP_S_HIER_LIST OPTIONAL
*" TABLES
*" I_T_LANGU TYPE SBIWA_T_LANGU
*" E_T_HIERS TYPE RSAP_T_HIERS
*" EXCEPTIONS
*" INVALID_CHABASNM_HCLASS
*" INVALID_HIERARCHY_FLAG
*" INVALID_HIERARCHY_SELECT
*" LANGU_NOT_SUPPORTED
*" HIERARCHY_NOT_FOUND
*" APPLICATION_ERROR
*"----------------------------------------------------------------------
* SEARCH_ENDDA =
* SEARCH_ROLETYPE =
* SEARCH_AGRTYPE =
* UPDATE_INDEX =
* IMPORTING
* ACT_WEGID =
* ACT_INT_WEGID =
* ACT_SVECT =
* ACT_BEGDA =
* ACT_ENDDA =
* ACT_TASK_CATA =
TABLES
ROOTS = t_roots
* NREL_ROOTS =
* EXCEPTIONS
* NO_STRU_SEARK = 1
* OTHERS = 2
.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* ENDLOOP.
loop at t_roots.
SELECT * FROM hrp1000
up to 1 rows
WHERE plvar = '01'
AND otype = t_roots-otype
AND objid = t_roots-objid
AND istat = '1'
AND begda le sy-datum
AND endda ge sy-datum.
ENDSELECT.
if sy-subrc eq 0.
i_rshiertrsf-chabasnm = I_S_HIEBAS-CHABASNM.
move t_roots-objid to i_rshiertrsf-hienm.
move hrp1000-short to i_rshiertrsf-txtsh.
move hrp1000-stext to i_rshiertrsf-txtmd.
move hrp1000-stext to i_rshiertrsf-txtlg.
append i_rshiertrsf.
endif.
endloop.
* i_rshiertrsf-chabasnm = I_S_HIEBAS-CHABASNM.
* i_rshiertrsf-hienm = 'RESPONSIBLE'.
* append i_rshiertrsf.
APPEND LINES OF I_RSHIERTRSF TO E_T_HIERS.
ENDFUNCTION.
Click on Create new entries-button and enter the line specified below.
Then in the left column, double-click on Evaluation path (individual ) and enter following values :
Before you can execute this, please create and run the program mentioned in appendix.
When you run the program, enter a new InfoObject name (not an existing one, since the program might
overwrite existing datasource definitions) in field P_IOBJ.
As second parameter enter a name for your DataSource in field P_DSCRCE.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
2007 SAP AG 15
How to Create a Hierarchy Extractor for Employees and their Department Managers
If you want this program to actually create the DataSource and update the necessary tables, check the
box for P_UPDATE.
Use transaction RSA1 or RSD1 to create the InfoObject you have specified in the previous step. Specify
for this object that it is using Hierarchies Hierarchies, not time-dependent.
Then use the button External Chars. In Hierarchies. This to include also the Organization Unit object, so
that these are included in your hierarchy and which allow you to verify the result with the Organizational
Structure used in the source system.
From the list of Characteristics, choose 0ORGUNIT.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
2007 SAP AG 16
How to Create a Hierarchy Extractor for Employees and their Department Managers
Create an InfoPackage for the Hierarchy on the InfoObject and press the button Available hierarchies
from OLTP. This will show you the available root nodes from you source system.
After you have selected one of the hierarchies and successfully loaded on, go and check the result (either
via the monitor of the InfoPackage (using the tree-button) or via the InfoObject maintenance using the
button Maintain Hierarchies)
After loading, this is the result. The hierarchy contains personnel numbers, mixed with the IDs of the
Organizational Unit included. If you want to have the description for the org. units, you can load the texts
using the standard extractor.
SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com
2007 SAP AG 18
How to Create a Hierarchy Extractor for Employees and their Department Managers
*&---------------------------------------------------------------------*
*& Report ZBW_CREATE_EMPL_HIER_EXTRACTOR
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT ZBW_CREATE_EMPL_HIER_EXTRACTOR.
tables :
roohiecat,
roohiecom,
rodcha,
rodchabas,
roosfield,
roosource,
roosourcet,
roosseg,
rohiebas
.
start-of-selection.
Copyright
Copyright 2007 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 changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or
registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks 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 are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web 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 for technology invented and 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 services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries 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 AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors
or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in
the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that
may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. SAP has no control over the information that you may access through the use of hot links contained in these materials
and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.
Any software coding and/or code lines/strings (Code) included in this documentation are only examples and are not intended to be
used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of
certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for
errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly
negligent.