Authorization
Applies to:
ECC 6.0. For more information, visit the ABAP homepage.
Summary
The paper is about what all steps related to creation of Customized table, table maintenance through SM30
and Table Authorization.
Author:
Maheshsingh Mony
Author Bio
Maheshsingh Mony is working with Capgemini India. He has 3+ years of full time experience
in implementation of SAP BI projects, Migration, Rollout, and Support Projects. His expertise
includes SAP BI, ABAP.
Table of Contents.
Creating Customized tables for Table Maintenance .......................................................................................... 3
Create Authorization Object................................................................................................................................ 8
Table Maintenance Generator .......................................................................................................................... 11
Exceptions: .................................................................................................................................................... 12
Changing the Source Code of Table Maintenance. ......................................................................................... 13
Related Content ................................................................................................................................................ 21
Disclaimer and Liability Notice .......................................................................................................................... 22
Give the Description of the table and enter the Following Details.
1. Delivery Class
Delivery Class
Used for
Customer table, SAP may insert new data records, but may not overwrite or delete existing
data records. The customer namespace must be defined in table TRESC. (Use Report
RDDKOR54 here).
System table with its own namespaces for customer entries. The customer namespace must
be defined in table TRESC. (Use Report RDDKOR54 here.)
System table, data changes have the same status as program changes.
System table (e.g. table of the development environment) whose data is transported with its
own transport objects (e.g. R3TR PROG, R3TR TABL, etc.).
Maintenance and display of this Dictionary object is not possible in transaction SE16.
Transaction SE54 does not allow the generation of a maintenance dialog, which means
automatically that calling transactions SM30/SM34 for this Dictionary object is no longer possible.
Transaction SE16 allows the display function for this Dictionary object, but no maintenance.
Generation of a maintenance dialog for this Dictionary object is possible using transaction SE54.
Transaction SM30 does not allow maintenance and display functions for this Dictionary object
Display/maintenance allowed:
The usage of standard table maintenance tools is allowed:
Transaction SE16 allows the maintenance and display functions for this Dictionary object.
Note: If an SM30 maintenance dialog exists for this Dictionary object, it is called.
Transaction SE54 allows the generation of a maintenance dialog for this Dictionary object.
Transaction SM30 allows the display and maintenance functions for this Dictionary object.
Fields
Significance
LASTCHANGED
CHANGEDATE
CHANGE_TIME
COMMENTS
Once all the fields have been entered then click on Technical Settings and Enter the following details on the next
screen:-
Data Class: The data class defines the physical area of the database (for ORACLE the TABLESPACE) in which
your table is logically stored. If you choose a data class correctly, your table will automatically be assigned to the
correct area when it is created on the database.
The most important data classes are (other than the system data):
APPL0
Master data
APPL1
Transaction data
APPL2
Master data is data which is frequently read, but rarely updated. Transaction data is data which is frequently
updated. Organizational und customizing data is data which is defined when the system is initialized and then
rarely changed.
There are two more data classes available, USR and USR1. These are reserved for user developments. The
tables assigned to these data classes are stored in a table space for user developments.
Note: The data class only has an effect on table storage for the database systems ORACLE and INFORMIX
Size category: The size category determines the probable space requirement for a table in the database.
You can select the categories 0 to 4 for your table. Each category is assigned a specific fixed storage area value in
the database. When you create a table, initial space is saved for it in the database. If more space is required later
as a result of data that has been entered, the storage space is increased in accordance with the category selected.
Press F4 on the field Size category to see the number of data records that can be maintained for the individual
categories of your table without complications ensuing. These complications could be for example a reorganization
becoming necessary because the maximum space to be reserved for the table was exceeded due to the
maintained size category.
Buffering status: The buffering status specifies whether or not a table may be buffered.
This depends on how the table is used, for example on the expected volume of data in the table or on the type of
access to a table. (Mainly read or mainly write access to the table. In the latter case, for example, one would not
select buffering).
You should therefore select
Buffering type: The buffering type defines whether and how the table should be buffered.
There are the following types of buffering:
single-record buffering
generic area buffering
full buffering
In generic area buffering, a number of key fields between 1 and no. of key fields-1 must be specified.
No. of key fields for generic buffers: If you read a record from a generically buffered table, all records whose the
left-justified part of the key corresponds to that of this record (generic key fields) are loaded into the buffer.
This left-justified part of the key is determined in this field by entering a number n of key fields. The first n key fields
of the table are thus the generic key fields.
Then the next screen will give a list of Authorization Objects already present in the system. You can
Select one of them from the avaliable list as per the requirement.
But if the table demands a new authorization object then click on New Entries pushbutton given on the
screen.
Enter the new authorization object name with its description as shown in the screen below. Certain
Naming convention is to be followed for the authorization object. (It should always start with Z).
Click on Save.
Enter the following details on the next screen:Authorization group - assigned/created for the table by following the procedure given in Section I.
Function Group - Name of the function group, to which the generated maintenance modules will belong.
Maintenance type According to the table requirement, any one should be selected.
One Step - Only one maintenance screen is processed during extended table maintenance. The
entries are displayed in list form on this screen.
Two Step - Two maintenance screens are processed during the extended table maintenance:
On the Overview screen the entries are displayed in list form.
On the Single screen one entry is displayed. The single screen can be called from the overview
screen, by function key, for every entry.
Maintenance Screen no. - According to the Maintenance type selected, overview screen and single screen
should be entered.
Recording routine Indicator for recording routine which should be used for the table contents.
Standard recording routine
No, or user, recording routine
Compare Flag This flag indicates whether the maintenance transaction allows the (checked) activation of
Business Configuration Sets (BC Sets), and the adjustment. This is the case if the maintenance transaction
can run in the background. There are four options present for the compare flag:
No Information
Not Adjustable
Adjustable in Dialog
Automatically Adjustable
5. Enter the logic to update the table with the parameters --> person responsible for making change,
timestamp etc. It is as shown below:-
7. Once you click on the Layout button the below screen will appear.
8. Enter the text to be displayed as the coloum heading in the output screen.
9. Change the attributes of the fields of table which are required to be non-editable as 'OUTPUT ONLY'.
i.e the fileds LASTCHANGED, CHANGEDATE and CHANGE_TIME.
The Coloumns would automatically be grayed out that would be uneditable in the output screen.
Create Transaction.
1. To create transaction, go to transaction SE93. Enter the transaction name which is to be created.
2. Click on Create.
6. Enter the created T-code and the below screen would appear as output.
7. Click on New Entries button to create an entry in the table. Enter the details and then click on SAVE.
8. As soon as you click on the save button the username,Date and Time appears automatically.
9. You can check the same data in the Se16 transaction for the table.
Related Content
http://forums.sdn.sap.com/thread.jspa?messageID=8393949#8393949
http://forums.sdn.sap.com/thread.jspa?messageID=8424845#8424845
http://forums.sdn.sap.com/thread.jspa?messageID=8620547#8620547
For more information, visit the ABAP homepage.