ZTABLE: Authorization Group

vallamuthu_madheswaran2 — Thu, 27 Dec 2007 13:06:55 GMT

Hi friends,

i am created a ztable and also created table maintanence generator.

now my problem is, i want to Auhorization Group or Authorization for particular table.

Thanks & Rgards,

Vallamuthu.M

Re: ZTABLE: Authorization Group

Former Member — Thu, 27 Dec 2007 13:25:22 GMT

No need of creating Auhorization Group give &NC&

Re: ZTABLE: Authorization Group

Former Member — Thu, 27 Dec 2007 16:08:00 GMT

hi,

If you want default authorization you can use &NC&.

but if you want specific roles to be assigned and then you can for new Zauth group .

you can create object class in SU20 /SU21 tcodes.

there you have to choose some class and then create Object by double clicking on that.

there you mention field names and actvt field.

actually Actvt = 03 Display

16 Execute

33 Read.

You can get all those entries in TDDAT table.

Regds

Sivaparvathi

Please reward points if helpful....

Re: ZTABLE: Authorization Group

Former Member — Fri, 28 Dec 2007 09:40:56 GMT

Hi this will solve ur problem.

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.

Sy-SUBRC values

4 User has no authorization in the SAP System for

such an action. If necessary, change the user

master record.

8 Too many parameters (fields, values). Maximum

allowed is 10.

12 Specified object not maintained in the user

master record.

16 No profile entered in the user master record.

24 The field names of the check call do not match

those of an authorization. Either the

authorization or the call is incorrect.

28 Incorrect structure for user master record.

32 Incorrect structure for user master record.

36 Incorrect structure for user master record.

with regards,

Hema Sundara

pls give points if u find this helpful.

topic Re: ZTABLE: Authorization Group in Application Development and Automation Discussions

ZTABLE: Authorization Group

Re: ZTABLE: Authorization Group

Re: ZTABLE: Authorization Group

Re: ZTABLE: Authorization Group