Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

regarding authorization objects

Former Member
0 Kudos

hello everyone,

how can i maintain check object in transaction se22 ? plz tell me the full procedure.


Former Member
0 Kudos

Please tell me, what can you do with SE22, because this transaction does not exist... (at least not in my system = ECC 6.0).

Also please explain what you want to do with a check object (do you mean a check table or something?).



Former Member
0 Kudos

Hi Vishal, follow this,

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:


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.







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

And a sample code for ur understanding.

c_auth TYPE sychar10 VALUE 'M_MSEG_WWA',"Auth. obj

c_act01 TYPE sychar02 VALUE '01'. "Activity 01(create)

LOOP AT fp_i_werks ASSIGNING <l_fs_werks>.


ID 'ACTVT' FIELD c_act01

ID 'WERKS' FIELD <l_fs_werks>-werks.

IF sy-subrc NE c_0.

*Mark for deletion for unauthorised plants.

<l_fs_werks>-werks = space.



the above code i implemented in my code.

first select the field which u want to check the authorization .

above code i wrote for werks(plant).

loop at werks internal table.

delcare the above syntax.

and do the same.

it will check each plant authorization.

kindly reward if found helpful.