authorization

Former Member — Thu, 03 Aug 2006 03:44:49 GMT

Hi all,

What is Authorization group and Authorization object.

How they work.

How to provide authority for a particular field.

Can anyone provide info.

Thanks in advance

Venkat

Re: authorization

Former Member — Thu, 03 Aug 2006 03:59:44 GMT

hi Venkat,

The access protection system must ensure that only authorized individuals have access to the system and to particular data. For achieving precise application security concerning authorization and to protect confidential data against unauthorized access it is very important to focus on the use of authorization groups.

The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. They usually occur in authorization objects together with an activity.

The table that contains all authorization objects is TOBJ.

The table that contains all activities is TACT.

The table that contains definition of all authorization groups is TBRG.

TBRG -- Contains all authorization groups and gives information about relation between authorization object and authorization group. The description of the authorization groups is defined in table TBRGT.

The field name for authorization group -- BRGRU -- is used to make additional restrictions on authorizations /e.g. for document maintenance/. In authorization objects and authorization checks, there are fields which are checked to verify user authorizations. Customizing objects are combined in authorization groups, and the authorization group is one of the two authorization fields, for example, in authorization object S_TABU_DIS which is in the object class BC_A (Basis - Administration). This object is for displaying or maintaining tables. It controls access using the standard table maintenance tool (transaction SM31), enhanced table maintenance (SM30) or the Data Browser (SE16), including access in Customizing.

Authorization object S_TABU_DIS has the following fields: DICBERCLS - Authorization group, maximum field length is four characters; and ACTVT - Activity (02: Add, change or delete table entries, 03: Only display table contents).

Generally, SAP standard tables are assigned to authorization groups. These assignments can be changed. You can then assign tables manually to a suitable authorization group. To do this, start Transaction SM30 for maintenance view V_DDAT, and create an entry for each of these tables. In V_DDAT is stored the assignment of Tables/Views to Authorization Groups. V_DDAT is cross-client; therefore, it can be viewed and used in all clients.

Note: If you don't make a selection, all tables maintained in Customizing transactions are assigned to authorization groups.

Check these links too..

http://help.sap.com/saphelp_crm50/helpdata/en/52/671285439b11d1896f0000e8322d00/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/52/67129f439b11d1896f0000e8322d00/frameset.htm

http://www.sap4.com/contentid-39.html

Go through these links you will get a good idea about the authorization concept:

su21 is used for maintenance of authority objects:

http://www.sap-img.com/basis/useful-sap-system-administration-transactions.htm

http://sap.ittoolbox.com/groups/technical-functional/sap-r3-basis/please-how-to-create-an-authorization-object-386391

http://web.mit.edu/ist/org/admincomputing/dev/abap_review_check_list.htm

Authorization object

Authorization Object are used to give authority to the user according to the position he or she is holding the organization unit.Different roles are assigned to the position of the organization unit and these roles in turn are assigned to the task.In SAP these task are assigned to the transactions .So the user is given authorization for the particular transaction.This way user are controlled from using the data which they are not supposed to accesss.Sometimes the authorizatio is only to read , that mean user can see the data but cannot change.

In some case the user is not eligible to see the data not relevant to his aera . eg. a sales rep in one sales area is not supposed to view the data of another sales area or sales rep.Even the user might be authorized for a transaction but the usage will be limited to area relevant to his /her work.

Authorization object is created in tcode SU21.

Authorization group

An authorization group contains tables and views with the same security requirements.In the Table maintenance dialog, you maintain the same gorup for tables that require similar authorizations.To activate the authorization, you must determine an activity for the authorization group in the authorizaton objects S_TABU_DIS & may be S_TABU_CLI. The link between the Auth group & auth Obj is in table TBRG.You can also assign authorization groups to tables to avoid users accessing tables using general access tools (such as transaction SE16). A user requires not only authorization to execute the tool, but must also have authorization to be permitted to access tables with the

relevant group assignments. For this case, we deliver tables with predefined assignments to authorization roups. The assignments are defined in table TDDAT; the checked authorization object is S_TABU_DIS.You can assign a table to authorization group Z000.(Use transaction SM30 for table TDDAT) A user that wants to access this table must have authorization object

S_TABU_DIS in his or her profile with the value Z000 in the field DICBERCLS (authorization group for ABAP Dictionary objects).

Check these links too..

http://help.sap.com/saphelp_crm50/helpdata/en/52/671285439b11d1896f0000e8322d00/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/52/67129f439b11d1896f0000e8322d00/frameset.htm

http://www.sap4.com/contentid-39.html

Reward if helpful

Regards,

Naveen