Skip to Content
avatar image
Former Member

Authorizationfield with versions in the Authorization Object

Dear All,

Could you please clear my doubt as and when we assign tcodes to the roles and after creating profile respective authorization objects and associated authorization fields of the tcode will get assigned to the profile.

But when I see in the authorization there I can find the multiple authorization fields with different versions.

Please find the below screenshot for your reference,

Regards,

Venkatesh

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jan 02, 2015 at 08:20 AM

    I have always wanted version management for my roles. Consider yourself very fortunate!  

    Cheers,

    Julius

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 02, 2015 at 07:17 AM

    inheritance was broken on kokrs field making it changed status. Hard to know more without see su24 proposal overview but I assume you only have single transaction resulting in proposal of that field.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 02, 2015 at 08:03 AM

    …400 was added with proposal for field KOKRS and you changed  it to “*”, so the status for authorization object is “CHANGED”

    …401 – was added because you don’t have identically filled authorization object with  status “STANDARD” or "MAINTAINED". Status "CHANGED" don't count.

    Add comment
    10|10000 characters needed characters exceeded