http://www.youtube.com/watch?

annotation_id=channel%3A96e95aa8-1847-224c-83b8e0cd302e2&feature=iv&src_vid=2vwjP7QX_NU&v=qxW_DGFpJnk
SAP ABAP VIDEOS
http://www.youtube.com/user/pcmoxon/videos

Indexes
The purpose of defining secondary indexes for tables is to enhance
the access time when performing select operations on the table.
The secondary indexes do actually occupy physical space in the
database; therefore, every table update implies a real updating of the
secondary indexes. So, defining secondary indexes helps the search
performance, they, however, slow down the updating process. For
this reason, tables in which entries are very frequently written
generally should only have a few indexes.
The database system sometimes does not use a suitable index for a
selection, even if there is one. The index used depends on the
optimizer used for the database system. You should therefore check
if the index you created is also used for the selection by using trace.
To create indexes for a table, from the main table maintenance
screen, select Goto _ Indexes from the menu or click on the Indexes
push button on the application toolbar. (Hernandez, 2000)

There are some view types like:

Database view is defined just the same way as it is de- fined in
the underlying database. It can use one or several related tables.
It supports the three relational operators: join, projection, and
selection. Only tables of type transparent are allowed for this
type of view.
Projection view. This type allows you to suppress some fields
from the display in a transparent table. The projection view is
defined using only the relational operator projection. Update,
insert, delete, and select operations can be performed.
- Structures are virtual tables that are made up of several tables.

Structures are comparable with tables of type INTTAB, internal

SAP tables.
-Help view. This type is used from transactions when additional
help is needed. Help views are used exclusively by the SAP help
system. All relational operators are supported. Access is only
possible with the SAP help and cannot be seen with either the
SAP Open SQL or the Native SQL. For the selection, a function
module is generated. For help view definitions only 1:1 and l:C
relationships are possible. This type ofview is activated using the
F4 function key.
Maintenance view.
These views enable the maintenance of a
group of related tables using standard SM30 transactions and
other special customizing transactions.

Lock Objects
In an information system where users can access the same data in a
concurrent way it is necessary to have a control system in charge of
granting the integrity and consistency of data. In the SAP R/3
system, this synchronization method for user access to data is built
on a datalocking mechanism by the definition and use of lock
objects over table records.
The locks are established and released by calling function modules
which are automatically generated when defining the lock objects in
the ABAP dictionary. This synchronization system is independent of
the locking mechanism used by the underlying DBMS. This section
introduces how lock objects are created, modified, and deleted with
some easy examples.
Creating Lock Objects. As previously introduced, a lock object is a

dictionary object of the type aggregate. A lock object definition then

has a similar structure to other aggregate type objects. Defining a
lock object requires the following steps:
1. Defining the attributes for the lock object
2. Choosing the secondary tables, selecting the arguments and
locking type
3. Activating the lock objects.