Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Buffering concept?

Former Member
0 Likes
8,283

Hi,

Can any one explain me buffering table concept in SAP Abap pls...

thanks in advance.

with regards

venkat

6 REPLIES 6
Read only

Former Member
0 Likes
5,125

Hi,

Buffering a table improves the performance when accessing the data records contained in the 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.

Could you please have a look at below link which will give details about buffering concept?

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f244446011d189700000e8322d00/frameset.htm

Thanks,

Vibha

Read only

Former Member
0 Likes
5,125

buffering is the concept of storing the table or program in a temporary memory space.

we can buffer one field or the whole table in the buffer.

Read only

Former Member
0 Likes
5,125

Definition

The name table (nametab) contains the table and field definitions that are activated in the SAP System. An entry is made in the Repository buffer when a mass activator or a user (using the ABAP Dictionary, Transaction SE11) requests to activate a table. The corresponding name table is then generated from the information that is managed in the Repository.

The Repository buffer is mainly known as the nametab buffer (NTAB), but it is also known as the ABAP Dictionary buffer

The description of a table in the Repository is distributed among several tables (for field definition, data element definition and domain definition). This information is summarized in the name table. The name table is saved in the following database tables:

• DDNTT (table definitions)

• DDNTF (field descriptions)

The Repository buffer consists of four buffers in shared memory, one for each of the following:

Table definitions TTAB buffer Table DDNTT

Field descriptions FTAB buffer Table DDNTF

Initial record layouts IREC buffer Contains the record layout initialized depending on the field type

There are two kinds of table buffers:

• Partial table buffers

• Generic table buffers

Check this link for more details.

http://www.abapprogramming.blogspot.com/2007/11/buffering-in-sap-abap.html

Regards,

Maha

Read only

Former Member
0 Likes
5,125

Hi,

THERE R 3 TYPES OF BUFFERING FOR A TABLE:-

1. Full table buffering :- here entire database table buffered to application server.

So further access to same table can be access from application server so, which interm reduces database traffic.

Fullbuffering can only applies to tables which have less data and rarely changed.

Ex-tcodes, company master data like T100, etc

2. single record buffering:- here only one record can buffered to application server by select single…………… with where all key fields can be specified .

Here if no record exists then also no record information stored to application.

Here it applies to database table which is larger in size and modified frequently.

3. Generic buffering:- here few database table records which matches can buffered to application server depends on generic keyfields(key fields specified while setting buffer settings).

So further access to same table can be access from application server so, which inters reduces database traffic.

Full buffering can only applies to tables which have less data and rarely changed.

Ex-tcodes, company master data like T100, etc

process at application server:-

4. if same table can access on multiple application servers then

All of them try to modify that table then it can be noted in DDLOG table with entry.

And their application servers can invoke when they are modifying that table can read the entry in DDLOG table and if found then they refresh that table and reload again.

NOTE:-here select with key fields can be mentioned else buffered tables can re read by next select can not read from buffer area

Read only

Former Member
0 Likes
5,125

Buffering is Howmany rows shouldbe fetched from the DB table in each hit. according to the value entered space is created in runtime to store data.

Reward if useful

Regards

ANUPAM

Read only

Former Member
0 Likes
5,125

Hi this will serve ur purpose:

We have 3 types of buffering

There are the following types of buffering:

o single-record buffering

o generic area buffering

o full buffering

Single-record buffering should be selected when :

o For large tables where there are frequent single-record accesses (using SELECT SINGLE ...). The size of the records being accessed should be between 100-200 KB.

o For comparatively small tables for which the access range is large, it is normally advisable to opt for full buffering. Only one database access is required to load such a table for full buffering,

while single-record buffering calls for a very large number of table accesses.

And also check this matter.

Single-record buffering: Only the records of a table that are really accessed are loaded into the buffer

Single-record buffering should be used particularly for large tables where only a few records are accessed with SELECT SINGLE. The size of the records being accessed should be between 100 and 200 KB.

Full buffering is usually more suitable for smaller tables that are accessed frequently. This is because only one database access is necessary to load such a table with full buffering, whereas several database accesses are necessary for single-record buffering.

Check this link :

http://help.sap.com/saphelp_nw04/helpdata/en/f7/e4c5a8a84a11d194eb00a0c929b3c3/content.htm

with regards,

Sowjanya.B

reward if helpful.