You are on page 1of 6

I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
BW365 Lesson: StructuraI Authorizations BI/mySAP ERP HCM
Lesson: StructuraI Authorizations BI/mySAP ERP HCM
Lesson Overview
This lesson deals with the topic oI automated authorization generation speciIic to
structural authorizations Irom mySAP ERP Human Capital Management (old name:
HR).
Lesson Objectives
AIter completing this lesson, you will be able to:
· Generate structural authorizations Irom mySAP ERP HCM in BI
Business ExampIe
You have implemented structural authorizations oI the component mySAP ERP HCM
in a mySAP ERP source system oI BI. You want to use these authorizations in the
same way in BI, avoiding duplicate maintenance.
StructuraI Authorizations in mySAP ERP HCM
Structural authorizations, Irom a business point oI view, have the same Iunction as the
general authorizations in mySAP ERP HCM or other SAP components and regulate
the access speciIic to data that is stored in time-dependent structures (organization
structures, event hierarchies, qualiIication catalogs, and so on).
Figure 93: StructuraI Authorizations - Organization of the Structure
2006/Q2 © 2006 SAP AG. All rights reserved. 243
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
Unit 8: Appendices BW365
Prerequisites
The data that you want to protect has to be located in a hierarchical structure
oI a personnel development component (organi:ation management, personnel
aevelopment, event management, etc.).
Features
Using the structural authorization check, you can assign authorizations Ior objects
that are located within the hierarchical structure and, Ior example, by speciIying a
root object you can determine that all objects that are located in the hierarchy under
this speciIic object can be changed. This concept ensures that even when there is a
change within the structure, the maintenance eIIort Ior structural authorizations will
be minimal. At the same time, we can guarantee that users continue to only have
access to the objects Ior which they are responsible. This Ilexibility is achieved,
on the one hand, by using the (initial) structure in organization management to
deIine the authorization proIile, and on the other hand, using a concept to store the
authorization proIile so that the system reacts automatically/dynamically to changes in
the organization structure or adapts the various proIiles automatically.
Authorizations using organizational structures
· Authorizations are assigned indirectly using organizational structures
Organizational Units
Job
Position
Task
· Advantages
Maintenance is easier because authorizations are changed accordingly
when there are structural changes
Clear
Limitation
Structural authorizations are very powerIul, thus the Iollowing aspects should
absolutely be considered:
· In addition to structural authorizations, the general authorizations could also be
used, which means mapping the structural authorizations in SAP alone may
not be suIIicient.
· Authorization requirements in SAP can be diIIerent Irom those in the source
system so that the standard mapping oI Business Content may not IulIil the
requirements.
244 © 2006 SAP AG. All rights reserved. 2006/Q2
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
BW365 Lesson: StructuraI Authorizations BI/mySAP ERP HCM
Procedure
· A prerequisite is that structural authorizations are already created. II not, then
these should still be done as part oI the mySAP ERP HCM project.
· There are appropriate objects Ior this in Business Content with which the
structural authorizations can be loaded (DataSources, InIoSources, DataStore
Objects). These should be activated.
· Scheduling data loading
· Scheduling or manual execution oI generation as with the automatic generation
scenarios that were already introduced
For structural authorizations, there is special Business Content that includes the
entire data Ilow. Otherwise, it is a generation scenario Ior DataStore Objects as was
already mentioned. An overview oI the objects and the data Ilow can be Iound in the
Iollowing Iigure.
Figure 94: Overview of Data FIow for StructuraI Authorizations
The Iollowing steps are necessary to provide the required data in BI.
· The users Ior which authorizations were extracted should be entered into the
table T77UU (user data are kept in the SAP memory this way)
· Generation oI indexes using the report RHAUS00 in the INDX index cluster
The data can be loaded into the DataStore Objects 0PA¸DS02 and 0PA¸DS03 using
the Business Content data sources 0HR¸PA¸2 and 0HR¸PA¸3.
2006/Q2 © 2006 SAP AG. All rights reserved. 245
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
Unit 8: Appendices BW365
Caution: The DataStore Object 0PA¸DS02, due to its structure and Iunction,
corresponds to the DataStore Object 0TCA¸DS01 (the general template
Ior generation oI value authorizations) and 0PA¸DS03 corresponds to
0TCA¸DS02 (hierarchy authorizations).
As Ior the general case oI authorization generation, the Iollowing steps must occur:
· the associated characteristics have to have been deIined relevant to authorizations
in BI Ior the organization structures (Ior example 0ORGUNIT).
· the data has to be loaded into the DataStore Objects accordingly.
· the generation Ior an authorization object that includes the associated
authorization relevant characteristics has to take place.
246 © 2006 SAP AG. All rights reserved. 2006/Q2
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
BW365 Lesson: StructuraI Authorizations BI/mySAP ERP HCM
Lesson Summary
You should now be able to:
· Generate structural authorizations Irom mySAP ERP HCM in BI
2006/Q2 © 2006 SAP AG. All rights reserved. 247
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
I

n

t

e

r

n

a

l




U

s

e




S

A

P




P

a

r

t

n

e

r




O

n

l

y
Unit Summary BW365
Unit Summary
You should now be able to:
· Show the runtime oI the authorization check.
· Generate structural authorizations Irom mySAP ERP HCM in BI
248 © 2006 SAP AG. All rights reserved. 2006/Q2

 Only /HVVRQ 2EMHFWLYHV $IWHU FRPSOHWLQJ WKLV OHVVRQ \RX ZLOO EH DEOH WR ‡ *HQHUDWH VWUXFWXUDO DXWKRUL]DWLRQV IURP P\6$3 (53 +&0 LQ %. Internal Partner %XVLQHVV ([DPSOH <RX KDYH LPSOHPHQWHG VWUXFWXUDO DXWKRUL]DWLRQV RI WKH FRPSRQHQW P\6$3 (53 +&0 LQ D P\6$3 (53 VRXUFH V\VWHP RI %. <RX ZDQW WR XVH WKHVH DXWKRUL]DWLRQV LQ WKH VDPH ZD\ LQ %. DYRLGLQJ GXSOLFDWH PDLQWHQDQFH Use 6WUXFWXUDO $XWKRUL]DWLRQV LQ P\6$3 (53 +&0 SAP SAP 6WUXFWXUDO DXWKRUL]DWLRQV IURP D EXVLQHVV SRLQW RI YLHZ KDYH WKH VDPH IXQFWLRQ DV WKH JHQHUDO DXWKRUL]DWLRQV LQ P\6$3 (53 +&0 RU RWKHU 6$3 FRPSRQHQWV DQG UHJXODWH WKH DFFHVV VSHFLILF WR GDWD WKDW LV VWRUHG LQ WLPHGHSHQGHQW VWUXFWXUHV RUJDQL]DWLRQ VWUXFWXUHV HYHQW KLHUDUFKLHV TXDOLILFDWLRQ FDWDORJV DQG VR RQ.

 Partner Internal Use Only )LJXUH  6WUXFWXUDO $XWKRUL]DWLRQV  2UJDQL]DWLRQ RI WKH 6WUXFWXUH 4 ‹  6$3 $* $OO ULJKWV UHVHUYHG  .

8QLW  $SSHQGLFHV %: 3UHUHTXLVLWHV 7KH GDWD WKDW \RX ZDQW WR SURWHFW KDV WR EH ORFDWHG LQ D KLHUDUFKLFDO VWUXFWXUH RI D SHUVRQQHO GHYHORSPHQW FRPSRQHQW RUJDQL]DWLRQ PDQDJHPHQW SHUVRQQHO GHYHORSPHQW HYHQW PDQDJHPHQW HWF.

 )HDWXUHV 8VLQJ WKH VWUXFWXUDO DXWKRUL]DWLRQ FKHFN \RX FDQ DVVLJQ DXWKRUL]DWLRQV IRU REMHFWV WKDW DUH ORFDWHG ZLWKLQ WKH KLHUDUFKLFDO VWUXFWXUH DQG IRU H[DPSOH E\ VSHFLI\LQJ D URRW REMHFW \RX FDQ GHWHUPLQH WKDW DOO REMHFWV WKDW DUH ORFDWHG LQ WKH KLHUDUFK\ XQGHU WKLV VSHFLILF REMHFW FDQ EH FKDQJHG 7KLV FRQFHSW HQVXUHV WKDW HYHQ ZKHQ WKHUH LV D FKDQJH ZLWKLQ WKH VWUXFWXUH WKH PDLQWHQDQFH HIIRUW IRU VWUXFWXUDO DXWKRUL]DWLRQV ZLOO EH PLQLPDO $W WKH VDPH WLPH ZH FDQ JXDUDQWHH WKDW XVHUV FRQWLQXH WR RQO\ KDYH DFFHVV WR WKH REMHFWV IRU ZKLFK WKH\ DUH UHVSRQVLEOH 7KLV IOH[LELOLW\ LV DFKLHYHG RQ WKH RQH KDQG E\ XVLQJ WKH LQLWLDO.

VWUXFWXUH LQ RUJDQL]DWLRQ PDQDJHPHQW WR GHILQH WKH DXWKRUL]DWLRQ SURILOH DQG RQ WKH RWKHU KDQG XVLQJ D FRQFHSW WR VWRUH WKH DXWKRUL]DWLRQ SURILOH VR WKDW WKH V\VWHP UHDFWV DXWRPDWLFDOO\G\QDPLFDOO\ WR FKDQJHV LQ WKH RUJDQL]DWLRQ VWUXFWXUH RU DGDSWV WKH YDULRXV SURILOHV DXWRPDWLFDOO\ $XWKRUL]DWLRQV XVLQJ RUJDQL]DWLRQDO VWUXFWXUHV ‡ $XWKRUL]DWLRQV DUH DVVLJQHG LQGLUHFWO\ XVLQJ RUJDQL]DWLRQDO VWUXFWXUHV ± 2UJDQL]DWLRQDO 8QLWV ± -RE ± 3RVLWLRQ ± 7DVN $GYDQWDJHV ± 0DLQWHQDQFH LV HDVLHU EHFDXVH DXWKRUL]DWLRQV DUH FKDQJHG DFFRUGLQJO\ ZKHQ WKHUH DUH VWUXFWXUDO FKDQJHV &OHDU Internal Partner Only Use SAP SAP Partner Use ‡ Internal ± /LPLWDWLRQ Only 6WUXFWXUDO DXWKRUL]DWLRQV DUH YHU\ SRZHUIXO WKXV WKH IROORZLQJ DVSHFWV VKRXOG DEVROXWHO\ EH FRQVLGHUHG ‡ .Q DGGLWLRQ WR VWUXFWXUDO DXWKRUL]DWLRQV WKH JHQHUDO DXWKRUL]DWLRQV FRXOG DOVR EH XVHG ZKLFK PHDQV PDSSLQJ WKH VWUXFWXUDO DXWKRUL]DWLRQV LQ 6$3 DORQH PD\ QRW EH VXIILFLHQW $XWKRUL]DWLRQ UHTXLUHPHQWV LQ 6$3 FDQ EH GLIIHUHQW IURP WKRVH LQ WKH VRXUFH V\VWHP VR WKDW WKH VWDQGDUG PDSSLQJ RI %XVLQHVV &RQWHQW PD\ QRW IXOILO WKH UHTXLUHPHQWV ‡  ‹  6$3 $* $OO ULJKWV UHVHUYHG 4 .

P\6$3 (53 +&0 3URFHGXUH ‡ ‡ $ SUHUHTXLVLWH LV WKDW VWUXFWXUDO DXWKRUL]DWLRQV DUH DOUHDG\ FUHDWHG .QIR6RXUFHV 'DWD6WRUH 2EMHFWV.%: /HVVRQ 6WUXFWXUDO $XWKRUL]DWLRQV %.I QRW WKHQ WKHVH VKRXOG VWLOO EH GRQH DV SDUW RI WKH P\6$3 (53 +&0 SURMHFW 7KHUH DUH DSSURSULDWH REMHFWV IRU WKLV LQ %XVLQHVV &RQWHQW ZLWK ZKLFK WKH VWUXFWXUDO DXWKRUL]DWLRQV FDQ EH ORDGHG 'DWD6RXUFHV .

 ‡ ‡ 7KH XVHUV IRU ZKLFK DXWKRUL]DWLRQV ZHUH H[WUDFWHG VKRXOG EH HQWHUHG LQWR WKH WDEOH 788 XVHU GDWD DUH NHSW LQ WKH 6$3 PHPRU\ WKLV ZD\. 7KHVH VKRXOG EH DFWLYDWHG 6FKHGXOLQJ GDWD ORDGLQJ 6FKHGXOLQJ RU PDQXDO H[HFXWLRQ RI JHQHUDWLRQ DV ZLWK WKH DXWRPDWLF JHQHUDWLRQ VFHQDULRV WKDW ZHUH DOUHDG\ LQWURGXFHG Only ‡ ‡ Internal Partner )RU VWUXFWXUDO DXWKRUL]DWLRQV WKHUH LV VSHFLDO %XVLQHVV &RQWHQW WKDW LQFOXGHV WKH HQWLUH GDWD IORZ 2WKHUZLVH LW LV D JHQHUDWLRQ VFHQDULR IRU 'DWD6WRUH 2EMHFWV DV ZDV DOUHDG\ PHQWLRQHG $Q RYHUYLHZ RI WKH REMHFWV DQG WKH GDWD IORZ FDQ EH IRXQG LQ WKH IROORZLQJ ILJXUH Use SAP SAP Partner Internal Use Only )LJXUH  2YHUYLHZ RI 'DWD )ORZ IRU 6WUXFWXUDO $XWKRUL]DWLRQV 7KH IROORZLQJ VWHSV DUH QHFHVVDU\ WR SURYLGH WKH UHTXLUHG GDWD LQ %.

1'. LQGH[ FOXVWHU 7KH GDWD FDQ EH ORDGHG LQWR WKH 'DWD6WRUH 2EMHFWV 3$B'6 DQG 3$B'6 XVLQJ WKH %XVLQHVV &RQWHQW GDWD VRXUFHV +5B3$B DQG +5B3$B 4 ‹  6$3 $* $OO ULJKWV UHVHUYHG  . *HQHUDWLRQ RI LQGH[HV XVLQJ WKH UHSRUW 5+$86 LQ WKH .

8QLW  $SSHQGLFHV %: &DXWLRQ 7KH 'DWD6WRUH 2EMHFW 3$B'6 GXH WR LWV VWUXFWXUH DQG IXQFWLRQ FRUUHVSRQGV WR WKH 'DWD6WRUH 2EMHFW 7&$B'6 WKH JHQHUDO WHPSODWH IRU JHQHUDWLRQ RI YDOXH DXWKRUL]DWLRQV.

DQG 3$B'6 FRUUHVSRQGV WR 7&$B'6 KLHUDUFK\ DXWKRUL]DWLRQV.

 $V IRU WKH JHQHUDO FDVH RI DXWKRUL]DWLRQ JHQHUDWLRQ WKH IROORZLQJ VWHSV PXVW RFFXU ‡ WKH DVVRFLDWHG FKDUDFWHULVWLFV KDYH WR KDYH EHHQ GHILQHG UHOHYDQW WR DXWKRUL]DWLRQV LQ %. IRU WKH RUJDQL]DWLRQ VWUXFWXUHV IRU H[DPSOH 25*81.7.

 WKH GDWD KDV WR EH ORDGHG LQWR WKH 'DWD6WRUH 2EMHFWV DFFRUGLQJO\ WKH JHQHUDWLRQ IRU DQ DXWKRUL]DWLRQ REMHFW WKDW LQFOXGHV WKH DVVRFLDWHG DXWKRUL]DWLRQ UHOHYDQW FKDUDFWHULVWLFV KDV WR WDNH SODFH Internal Only ‡ ‡ Partner Use SAP SAP Partner Internal Use Only  ‹  6$3 $* $OO ULJKWV UHVHUYHG 4 .

Internal Partner Only Use SAP SAP Partner Internal Use Only 4 ‹  6$3 $* $OO ULJKWV UHVHUYHG  .%: /HVVRQ 6WUXFWXUDO $XWKRUL]DWLRQV %.P\6$3 (53 +&0 /HVVRQ 6XPPDU\ <RX VKRXOG QRZ EH DEOH WR ‡ *HQHUDWH VWUXFWXUDO DXWKRUL]DWLRQV IURP P\6$3 (53 +&0 LQ %.

8QLW 6XPPDU\ %: 8QLW 6XPPDU\ <RX VKRXOG QRZ EH DEOH WR ‡ 6KRZ WKH UXQWLPH RI WKH DXWKRUL]DWLRQ FKHFN ‡ *HQHUDWH VWUXFWXUDO DXWKRUL]DWLRQV IURP P\6$3 (53 +&0 LQ %. Internal Partner Only Use SAP SAP Partner Internal Use Only  ‹  6$3 $* $OO ULJKWV UHVHUYHG 4 .