Is the authorization behave correctly ?

[Former Member]

Hi,

Assume I have a pers. no. belonging to Pers. Area A (belonging to Org. Unit A), Position S1 from 01.01.2008 - 31.08.2009. Subsequently, from 01.09.2009 - 31.12.9999, the pers. no is transferred to Pers. Area B (belonging to Org. Unit B) and Position S2.

The PA administrator of Pers. Area A is granted all the PA infotypes (including IT1) of persons belonging to Pers. Area A and structural auth. to access all the OSP (OU, Position and Person) belonging to Org. Unit A. When this PA administrator runs a simple PA (run date = today) report for key date as at 31.07.2009, the program (which is linked to Logical database PNP) prompts that the administrator has insufficient authorization. The simple PA report is as follows :

REPORT ...

TABLES : PERNR.

INFOTYPE : 0001.

GET PERNR.

WRITE : / P0001-PERNR.

Can someone explain why is it so ? I presume that the administrator has authorization to access this pers. no as at 31.07.2009 which is prior to the transfer. If I remove the structural authorization, the output is correctly produced. The structural auth. is based on :

- Plan Version 01

- Obj Type O

- Object ID : Org Unit A

- Evaluation Path : OSP

- Status Vector : 1

Why is the structural authorization hinders the access to the data as at 31.07.2009 of this pers. no. ?

Thank you.

Regards

KC

[Former Member · Accepted solution]

Have the user run SU53 immediately after he is stopped. This should show you what authorization issues are in play.

Kirsten

[Former Member · Accepted solution]

Dear Kirsten,

Yes, su53 shows IT1 authorization is missing. I am running against key date 31.07.2009 in which the administrator would still have authorization to access the pers. no's IT1 for records prior to the transfer. The administrator can view via PA20 but not via report. That is what puzzles me. Thank you.

Regards

KC

[ted_dinh]

What value do you config for 'Period' in the 'Authorization Profile' ?

[Former Member]

Hi Ted,

The period value is left blank. I have found a "workaround" for the issue. One has to place the following code in the report :

INITIALIZATION.

PNP_SW_SKIP_PERNR = 'N'.

Thank you all.

Regards

KC

[ted_dinh]

Kir :

Great. Just fyi, OSS note 525585 explains the exact authorization behavior you experienced on how SAP would re-act if the ee moves out of the area where the admin has authorization as far as reporting goes .

Rgds.