‎2007 Apr 04 9:53 AM
Hi,
I want to know wht is the purpose of Authorization Check? please provide me some documents so that i can refer that?
with regards
Faisal
‎2007 Apr 04 9:57 AM
Hi Faisal,
To Assign Authorization Group
The Authorization group can be created as follows
Transaction SE54 >Select 'Authorization Groups'>Create/Change-->New Entries.
Now the authorization group created can be assigned to your table.
When you doesn't want the every user to access the Object developed you have to restrict the user , so you create an authorization object for an orgn unit and provide values like Create/change /display(01,02,03 for ACTVT field).
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
Hope this resolves your query.
Reward all the helpful answers.
Regards
‎2007 Apr 04 9:56 AM
‎2007 Apr 04 9:57 AM
‎2007 Apr 04 9:57 AM
Hi Faisal,
To Assign Authorization Group
The Authorization group can be created as follows
Transaction SE54 >Select 'Authorization Groups'>Create/Change-->New Entries.
Now the authorization group created can be assigned to your table.
When you doesn't want the every user to access the Object developed you have to restrict the user , so you create an authorization object for an orgn unit and provide values like Create/change /display(01,02,03 for ACTVT field).
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
Hope this resolves your query.
Reward all the helpful answers.
Regards
‎2007 Apr 04 9:58 AM
Authorization check helps to restrict the users to access some transaction code/perform some task on SAP.
‎2007 Apr 04 10:03 AM
For concept look at SAP online help <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/bf/c9934258a5ca6ae10000000a155106/content.htm">Restricting Access - Authorization Concept</a>
For programmation look at <a href="http://articles.techrepublic.com.com/5100-6329_11-5110893.html">Comprehend the SAP Authorization concept with these code samples</a>
Regards