Question:
When using the RH_GET_ORG_ASSIGNMENT function module to determine the HR structural authorisation I am experiencing a system update issue when I move an employee.
For instance, a person can only view the org unit (& any subordinate org units) to which they are assigned via their position. I then move that person in PA to another position and when executing transaction PPOSE and executing a structure search by Organizational Unit, I get the error message Object 01 O 50000376 does not exist (error message 5A 040) - object 50000376 being the org unit to which they were previously assigned. By using the Object Manager & executing a 'Search term' search I can now see the org unit(s) to which the person has been newly assigned. The next day this problem no longer appears.
I have therefore concluded that there must be some automatic generation program which is running overnight and updating certain system tables. Does anyone have any experience of the above and can provide some assistance.
I have also noticed that the structural authorisations seems to work regardless of the fact that there is a '0' assigned to the AUTSW/ORGPD switch. Again - am I missing something here?
Regards, Steve
Answer:
Hi SPW,
The parameter AUTSW/ORGPD activates structural auths in PA. Structural auths in PD are enabled by default.
As for your error message, not really sure.
For structural auths there are tables that get populated if you experience performance issues. Generally you schedule a regular batch job to update the table. The programs are RHBAUS00 - RHBAUS02.
When the user is entered in the table, the checks are no longer determined dynamically, but based on the table entry, if org structure and the table entries don't match.....? I don't think this is the problem as you would normally get an authorisation error not an error message.
Cheers
Peter
Answer:
Peter,
Thanks for the information but as you thought, it hasn't really solved the problem. However, on coming in this morning and re-testing the problem has resolved itself (as I previously mentioned). As I have not entries in T77UU the RHBAUS00 - RHBAUS02 reports do not help. So at the moment a bit of a mystery which I will progress with SAP via OSS unless someone else is able to offer any enlightenment.
With regard to your point about the AUTSW/ORGPD switch only activating structural auths for PA - can you tell me what this means i.e. if I leave the setting at '0' what does not work?
Thanks,
SPW
Answer:
Hi SPW,
If you leave it on 0 then structural auths don't work when you access employees via PA for example txn PA20, PA30.
The values are 0, 1, 2, 3, 4 at least on 4.6 and 4.7. The different values deal with how you handle non integrated employees.
Cheers
Peter
Answer:
Peter,
Thanks very much for that although I am intrigued by the numbers 2,3 & 4 - do you have any more information on what each of these switches does?
Also - one other issue I am finding with the PD structural auths is the one of inheritance of infotype 1017. I am assigned an auithorisation profile to an org unit - if I run report RHPROFL0 for this org unit it picks up the appropriate user master record. However, if I run the report for any subordinate org units it doesn't pick up the user master records - I find that I have to assign the authorisation profile to every org unit before report RHPROFL0 can work. This doesn't seem correct to me.
The settings for the authorisation profile in T77PR are as follows:
Profile HRORGCHI
No. 12
PV 01
Ob
ObjectID
EvalPath O-O-P
StatV 1
Depth
S
M X
Period Function module RH_GET_ORG_ASSIGNMENT
Sorry to burden you with all of this but you seem to know what you are talking about!!
Thanks,
SPW
Answer:
SPW,
The values for 1,2,3,4 are as follows
1 - Evaluate Org unit and deny auth by defualt
2 - Never evaluate org unit and deny auth by defualt
3 - Evaluate org unit and grant auth by defualt
4 - Never evaluate org unit and grant by default.
These setting deal with employees that don't hold positions i.e. 9999999 and are assigned to an org unit, then you should use 1 or 3.
1 is the more controlled option. 3 evaluates the org unit to see if it is in your structure, but grants access by default if they are NOT in AN org unit.
If your employees are in a default position and not assigned to an org unit then you should use 2 or 4.
For your issue with RHPROFL0, sounds interesting. I have never really assigned PD profiles at an Org unit level before and this does sound a bit odd. Are you using hte standard PRFL0 evaluation path?
Oher than that not sure at the moment
Answer:
Peter,
Thanks for the info. Yes, when using RHPROFL0 I am using the standard evaluation path PROFL0 however I have just discovered that the system is at HR Support Pack 69 - I believe the most up to date number is around 96!! with the last support pack having been applied in June 2003!! I have therefore decided to wait for the patch levels to be brought up to date (apparently happening in the next few days) before undertaking any more investigations.
Should the support pack updates solve the problem I will let you know, in the mean time many thanks for your assistance/advice to date.
Thanks,
SPW
Answer:
Patch upgrade solved the problem - hurrah.
However, requirements of client mean that I will not be using this solution anyway - Typical.
The client wants people to be able to see the information contained within their corporate org unit rather than just their deparmental org unit. Cannot be bothered to implement the function module RH_GET_MANAGER_ASSIGNMENT and associated A012 assignments due to the admin overhead this will cause the client post implementation.
Will therefore just give them a statically assigned org unit in T77PR with accompanying procedure for ongoing maintenance