Base Tables

[Former Member]

Hi Experts,

I am new to ABAP, any advisable on Base Tables.

Thanks,

Nirmala

[Former Member]

Hi

Many times ABAP programmers deal with base tables and nested selects. Instead it is always advisable to see whether there is any view provided by SAP on those base tables, so that the data can be filtered out directly, rather than specially coding for it.

Not recommended

Select * from zcntry where cntry like ‘IN%’.

Select single * from zflight where cntry = zcntry-cntry and airln = ‘LF’.

Endselect.

Recommended

Select * from zcnfl where cntry like ‘IN%’ and airln = ‘LF’.

Endselect.

reward me...

Regards,

Raghava

[Former Member]

thank you for your reply,

[Former Member]

hi,

Tables are defined in the ABAP/4 Dictionary and then created in the database. The construction of the data produced when calculations are carried out within programs or when data is transferred between programs can also be defined globally in the ABAP/4 Dictionary. This is achieved by means of Structures in the ABAP/4 Dictionary. A structure is defined in the ABAP/4 Dictionary like a table, but no table in the database corresponds to it

In R/3 there are three table types:

 transparent tables

 pooled tables

 cluster tables

A transparent table in the dictionary has a one to one relationship with a table in the database. Its structure in R/3 Data Dictionary corresponds to a single database table. For each transparent table definition in the dictionary, there is one associated table in the database. The database table has the same name, the same number of fields, and the fields have the same names as the R/3 table definition. When looking at the definition of an R/3 transparent table, it might seem like you are looking at the database table itself.

Transparent tables are much more common than pooled or cluster tables. They are used to hold application data. Application data is the master data or transaction data used by an application. An example of master data is the table of vendors ( called vendor master data )or table of customers ( called customer master data ). An example of transaction data is the orders placed by the customers, or the orders sent to the vendors.

Transparent tables are probably the only type of table you will need to ever create. Pooled and cluster tables are not usually used to hold application data but instead hold system data, such as system configuration information, or historical and statistical data.

Both pooled and cluster tables have many to one relationships with database tables. Both can appear as many tables in R/3, but they are stored as a single table in the database. The database table has a different name, different number of fields, and different field names than the R/3 table. The difference between the two types lies in the characteristics of the data they hold, and will be explained in the following sections.