cancel
Showing results for 
Search instead for 
Did you mean: 

Structural Authorization No Authorization during Validity Period

Former Member
0 Kudos

Hello Experts,

A user of ours is having issues maintaining an old record of a position. She can maintain current and future records, but records before a certain date she cannot maintain. When i use a firefighter ID I am able to make changes to the records. We are trying to determine what could be the root cause of the issue?

Also the O-S Relationship date is the cut off date beyond which the user cannot maintain the data, however the other Org Unit that the position had been moved from the User has access to that Org unit as well so we are unable to understand why the user cannot maintain data on that position in the past. Your prompt help would be highly appreciated!!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

You could try the following troubleshooting tactic:

  • Go to transaction PPST
  • Enter the root object used in the evaluation path of the structural authorizations setup
  • Enter the evaluation path which is used

In the output you will get a view on which objects are retrieved.

The position object to which your user does not have access to will probably not be included.

In this way you can find out which validity period gaps (validity periods of objects and their relationships) might be causing this issue.

Best regards,

Maxime

Former Member
0 Kudos

Thank you for your help, Maxime. The issue is that although the user has access to maintain that position, but the user cannot maintain any data for the position before the O-S relationship was established. However the Org Unit that the position was moved from the user has access to that Org Unit as well. So I am not sure why it is allowing her to maintain data for certain periods, but will not allow her to go beyond the O-S relationship date. Hope that makes sense.

Former Member
0 Kudos

The objects to which a user has access according to structural authorizations is determined by the validity periods by which these objects are linked.

Take the following example: O-O-S

  • relationship (infotype 1001) O-O has a validity period equal to 01.01.2016-31.12.9999
  • relationship (infotype 1001) O-S has a validity period equal to 01.01.1900-31.12.9999
  • all objects (infotype 1000) have a validity of 01.01.1900-31.12.9999

On date 31.12.2015 the user will not have access to the position because structural authorizations apply a cross-section to these validity periods.

Hope it helps.

Best regards,

Maxime

Former Member
0 Kudos

Thank you for your response, Maxime. It helped, but what if the person has access to the other Org Unit as well to which the position belonged on 12-31-2015 before it was moved on 01-01-2016? Why does structural authorization prevent the user from accessing the data then? Thanks.

Former Member
0 Kudos

Hi,

Can you check the selection period value set for the profile in OOSP?

Hope this helps.

Donnie

Former Member
0 Kudos

Thank you, Donnie. The period is left blank. Please see images below. Thanks.

Former Member
0 Kudos
Former Member
0 Kudos

Hello Donnie. It is assigned to All

Former Member
0 Kudos

Hello Maxime,

Like I said the user has access to both Org Units. The one in present and the past, but the system is still disallowing the user to maintain the position in the past.

Regards!

Answers (0)