Skip to Content
author's profile photo Former Member
Former Member

Restricting HR Tables fields via auth object?

Happy Holiday's everyone!

We have a custom tcode for Pricing Admin report which currenltly only has S_Tcode for an auth obj. It was combined in a role that we removed the HR authorization from and apparently these were interdependent but undocumented. Now the pricing transacation no longer functions.

Instead of just adding back the missing HR authorizations back into the custom Tcode I'm being asked if we can restrict PA00002 (the table being called in the program) to first name, last name and personnel number fields. Is there an authorization object that will let me restrict in this manner or do I need send this back to the developers to write in the code?

Or can I restict to these fields via authorization groups (something we are looking into implementing more next year).

Thanks

Kris Wise

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 12, 2011 at 05:40 PM

    That is a bad omen for the next year... 😉

    Try to change the code this year still to deliver only the fields you want from the infotype or go for an "existence check" which no authorization requirements as that is what you seem to be wanting.

    Being custom code, you should post the problematic part to discuss a solution.

    Cheers,

    Julius

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 13, 2011 at 12:24 PM

    Hi,

    It is not possible to restrict a part of IT0002 through Authorization Objects, neither with the concept of Authorization groups.

    The only way you can do it is through creation of a new screen element for IT0002 and using that in your ABAP Program. This is not Security's cup of tea.

    Thanks, Deb

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.