I create a cusomized Z-table and a view for it, all the table maintain genenator was done and ok, so there is diolog program SAPLZ* and screen generated for maintain the entries in Z-table, since we need a t-code with authorization object included, so i tried to create a t-code with this dialog program and the screen and put authorization object, but it got problem when it test it no matter i delete the authoirzation object.
What is the problem?!
Once you geenrate the table maintenance for that Z table
use the tcode SM30 to add/change the entries in that table.
If you wants to create a new Tcode you can create using the Transaction SE93
for authorization object 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.
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.
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.
'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.
Reward points if useful
But I just want to put all in the Z t-code, the problem is: at this moment, in the Z t-code, I only put the program name (table maintain generator program) and the screen number, and ticked GUI support, but I still get shortdump error when testing the Z t-cde.
I don't know why?!
You should create a Parameter transaction.
In proposed values, put SM30 and tick "skip initial screen".
Then at the bottom, complete the parameters:
VIEWNAME | put table name
SHOW | put X
Hope it helps
However, i think you should use integrated Maintenance view security instead of a separate Z transaction.
Sorry for delay. I meant entering Authorization group in SE55 transaction, where you define the maintenance view. I think from there you set the security over the maintenance view so you don't need any additional coding. But someone more experienced about this should confirm or clarify.