A

B A P&W E B D Y N P R O A B A P @ A R J U N

IGROWSOFT

Extended Table Maintenance Events

Im plementing Table maintenance Events The table maintenance generator screen is accessed either via SE54 or via SE11. SE11->Database Table->Utilities->Table Maintenance Generator. In the table maintenance generator screen follow the path Environment->Modification Events 2. In the Screen, Click on the new entries. Select a desired dialog event. 4. Now specify a form routine name. On clicking on the editor (the 3rd field in display), a new include name is proposed. Select the desired one and you can insert your lines of code here. Write the code inside a "FORM.... ENDFORM", since these routines are dynamically called corresponding to the dialog events w e have specified.We do not need to specify the PERFORM explicitly. The record created can be referred dynamically as <table-name> - <fieldname>. For exampleEx: The values can be assigned as: ZTRIAL-ZDATE = sy-datum General Case Study: Consider a case w hen we have to enter the timestamp w hen a record was created or entered in the table. This requirement is such that, the timestamp should be calculated only w hen the record is created, not at the time of saving. We create the required table w hich holds the information of customer in each company code.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 1

B A P&W E B D Y N P R O A B A P @ A R J U N
We create the table maintenance generator. And then create the event.

IGROWSOFT

Since this event has to be called during the creation of the record, w e choose the event - 05.

And insert this piece of code after creating a new include (click on the "Editior" tab).

After activating and running the SM30 transaction, we can get the field populated accordingly.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 2

B A P&W E B D Y N P R O A B A P @ A R J U N

IGROWSOFT

Technical Settings
When a table is created in the database one of the mandatory step is to assign the Technical settings to it. Technical settings are mainly used to define how the table w ill be handled w hen it is created in the database, that is w hether the table w ill be buffered and whether changes to data records of the table w ill be logged. With out this technical settings if w e try to activate the table it w ill give error.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 3

B A P&W E B D Y N P R O A B A P @ A R J U N

IGROWSOFT

The most important things w hich comes under Technical settings are

1) Data class 2) Size category Data class: By choosing data class some space will be allocated to the table in the database w hen it is created. Each data class corresponds to a physical area in w hich all the tables assigned to this data class are stored.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 4

B A P&W E B D Y N P R O A B A P @ A R J U N
There are 3 main data classes: a) APPL0- Which is the master data. Data w hich will be rarely changed. An example of master data can be like name, employee number and telephone number. b) APPL1-Which is transaction data. Data that is frequently changed. An example of transaction data is the goods in go dow n which will change as per the purchases.

IGROWSOFT

c) APPL2-Which is organizational data. Customizing data that is defined w hen the system is installed and rarely changed. Example may be table w ith country codes. By assigning the data class to the table w e can retrieve the data very easily. There are also 2 more data classes USR and USR1, w hich are provided for the customer. These are for the user developments. The tables assigned to these data classes are stored in a table space for user developments.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 5

B A P&W E B D Y N P R O A B A P @ A R J U N

IGROWSOFT

Size category: The size category defines the expected space required for the table in the database. Size category varies from 0 to 4 for your table. Each category is assigned a certain fixed memory size in the database, w hich depends on the database system used. When a table is created, initially w e w ill allot 1 size category among 0 to 4 then some space is reserved in the database called initial extent.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 6

B A P&W E B D Y N P R O A B A P @ A R J U N

IGROWSOFT

If more space is required at a later time due to more data entries, additional memory w ill be added depending on the selected size category. Suppose if 0 is selected then 0-10,000 records can be added. If at a given time if more records have to be added then again space for 10,000 more records will be allocated as extent area.Size category varies if a new field is added to the table. Size category also varies if data type and length changes.

By this size category we can prevent space from being w asted.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 7

B A P&W E B D Y N P R O A B A P @ A R J U N

IGROWSOFT

In addition to these w e also have Buffering permission: The buffering permission defines whether the table may be buffered. Here possibilities are: i) Buffering not permitted ii) Buffering permitted but not activated iii) Buffering activated Buffering type: Here w e have to define buffering type i.e. w hether it is full buffering, single-record buffering, or generic buffering. The buffering type defines how many table records are loaded into the buffer when a table entry is accessed. Logging: This tells w hether changes to the table entries should be logged. If it is maintained the each change to a table record is recorded in a log table.

Table Buffering
SAP Table Buffering Table buffering is used to reduce database load and improves the performance when accessing the data records contained in the database table. The table buffers reside locally on each application server in the system. The data of buffered tables can thus be accessed directly from the buffer of the application server. This avoids the time-consuming process of accessing the database. The options for selecting the Buffering 1. Buffering not allow ed Table is not required to buffer. 2. Buffering allowed but not activated For a database table buffering is allow ed , but at that point of moment buffering should not be active. 3. Buffering allowed if the table should be buffered. Table should be specified by a buffering type. Buffering Types: 1. Full buffering : In this buffering type, complete table or none of the table is in the buffer. If a read access is made to a record, all records of the table are transferred to the buffer. : This buffering type is part of the primary key of a table. When a table record is read, this buffer type loads all records that correspond with the generic key.

2.

Generic buffering

3.

Single- record buffering : In this buffering type, only the records of a table w hich are actually accessed are loaded into the buffer.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 8

B A P&W E B D Y N P R O A B A P @ A R J U N
How to Log the changes to table records?
1) Goto se11 transaction. 2) Give the name of the table for w hich you want to automatically log the changes for. 3) Press Display. 4) Click on Technical Settings Button on the Application Toolbar. 5) Check the "Log Data Changes" Check box at the end of the screen. 6) This flag w ould define whether change sto the data records of the table are to be logged or not.

IGROWSOFT

If logging is activated, then every change (Update/Delete) to an existing data record is recorded in the Standard Database Log table DBTABLOG. Note: Activating logging slow s down accesses that change the table. First of all, a record must be w ritten in the log table for each change. Secondly, many users access this log table in parallel. This could cause lock situations even though the users are w orking with different application tables.

AR J U N.LE ARN R E AL T I ME SC E N ARIOS DON E B Y ME

Page 9