To create custom transaction, it is suggested that
you define the naming convention as simple as possible to make sure that users
will remember the transaction and do not have to second guess. If a user needs
a custom transaction to browse table MARA, you can either call the transaction
ZSE16_MARA or simply ZMARA.
Use transaction SE93 to create new transactions and
define them as ‘Parameter Transaction’:
Enter SE16 into
the transaction field and select the flag the ‘skip initial screen’ field:
On the lower portion of the screen, enter the following information:
Name of screen field: DATABROWSE-TABLENAME
Value: Enter the name of the table you want to browse with SE16
When you save these
entries, you will be prompted to add this change to a development class and
transport. Use development class ZSEC for security or any other development
class recommended by the development team.
Add the changes into a transport
request and map the
new transaction to authorization
object with SU24.
Find out with transaction SE54 to what
authorization group the table(s) belongs to:
Once you have identified the authorization group, map
the newly created transaction to object S_TABU_DIS with display access only and
limited to the authorization group the table belongs to:
Add new transaction to
roles
You can now finally add
the new transaction to the roles according to the user request.
