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

Authorization Field Values

Does anyone know if there is a table in SAP ECC that provides all possible entry values for an authorization field? For example, I want to see what values I can select from for field PPFCODE.


Add comment
10|10000 characters needed characters exceeded

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 26, 2007 at 09:13 PM


    Check the following tables





    all above related to authorizations

    Check the Tcodes






    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 26, 2007 at 09:48 PM

    Hello Michael

    Using transaction SU21 (<i>List of authorization fields</i>) you can display the details for AUTH field PPFCODE. If you push the button <b>Input Help (Shift+F4)</b> you will get all 33 possible values (Note: my system is ECC 5.0).

    A very handy function module for your purpose is <b>SUSR_AUTF_GET_F4_HELP</b>. Simply call the function module with your AUTH field and it displays all search help values. There you should find a programmatic way to determine AUTH field values.



    Add comment
    10|10000 characters needed characters exceeded

    • Hello Michael

      Table <b>TACT </b>contains all possible activities.

      Table <b>TACTZ </b>contains the valid activities for each AUTH object.

      The values allowed for non-activity fields depends on the type of AUTH fields:

      - checktable (e.g. T001 for BUKRS)

      - fixed values in domain of AUTH field



  • author's profile photo Former Member
    Former Member
    Posted on Sep 28, 2007 at 06:05 AM


    In general different users will be given different authorizations based on their role in the orgn.

    We create ROLES and assign the Authorization and TCODES for that role, so only that user can have access to those T Codes.

    USe SUIM and SU21 T codes for this.

    Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An authorization check is implemented for every sensitive transaction.

    If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization check.

    This means you have to allocate an authorization object in the definition of the transaction.

    For example:

    program an AUTHORITY-CHECK.

    AUTHORITY-CHECK OBJECT <authorization object>

    ID <authority field 1> FIELD <field value 1>.

    ID <authority field 2> FIELD <field value 2>.


    ID <authority-field n> FIELD <field value n>.

    The OBJECT parameter specifies the authorization object.

    The ID parameter specifies an authorization field (in the authorization object).

    The FIELD parameter specifies a value for the authorization field.

    The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields.

    To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.

    Authorization : An authorization enables you to perform a particular activity in the SAP System, based on a set of authorization object field values.

    You program the authorization check using the ABAP statement AUTHORITY-CHECK.


    ID 'ACTVT' FIELD '02'


    IF SY-SUBRC <> 0.

    MESSAGE E...


    'S_TRVL_BKS' is a auth. object

    ID 'ACTVT' FIELD '02' in place 2 you can put 1,2, 3 for change create or display.

    The AUTHORITY-CHECK checks whether a user has the appropriate authorization to execute a particular activity.

    This Authorization concept is somewhat linked with BASIS people.

    As a developer you may not have access to access to SU21 Transaction where you have to define, authorizations, Objects and for nthat object you assign fields and values. Another Tcode is PFCG where you can assign these authrization objects and TCodes for a profile and that profile in turn attached to a particular user.

    Take the help of the basis Guy and create and use.

    <b>Reward if usefull</b>

    Add comment
    10|10000 characters needed characters exceeded