topic Re: regarding authorization objects. in Application Development and Automation Discussions

regarding authorization objects.

Former Member — Wed, 23 Jan 2008 06:31:46 GMT

hello everyone,

plz. tell me, what is authorization group?

Re: regarding authorization objects.

Former Member — Wed, 23 Jan 2008 06:35:12 GMT

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.

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.

Also check these links.

http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1191796,00.html

Regards,

Maha

Re: regarding authorization objects.

Former Member — Wed, 23 Jan 2008 06:41:15 GMT

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 ...

http://help.sap.com/saphelp_nw70/helpdata/en/35/26b17fafab52b9e10000009b38f974/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/52/671285439b11d1896f0000e8322d00/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6859e07211d2acb80000e829fbfe/content.htm

Re: regarding authorization objects.

Former Member — Wed, 23 Jan 2008 06:41:18 GMT

Hi Vishal, this helps u how to dreate an authorization group.

Gotot SU21 tcode and create a Class or create an Auth Object under a class in it

see the doc

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.

http://help.sap.com/saphelp_nw04s/helpdata/en/52/67167f439b11d1896f0000e8322d00/content.htm

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.

AUTHORITY-CHECK OBJECT 'S_TRVL_BKS'

ID 'ACTVT' FIELD '02'

ID 'CUSTTYPE' FIELD 'B'.

IF SY-SUBRC 0.

MESSAGE E...

ENDIF.

'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.

kindly reward if found helpful.

cheers,

Hema.