1.3.11

SAP Note 23877 - Performance: Buffering condition tables

Symptom:

Perfomance problems with condition tables.

This note applies to the following tables.

Table
(Condition table) Description

A001 - A999 Pricing tables
B001 - B999 Output tables
C001 - C999 Account determination tables
KOT+001 - KOT+999 Listing table, Exclusion table, Material determination tables ...

Additional key words

Condition table, performance, database, buffering
message: TK203

Cause and prerequisites

Configuration error.

Solution
When generating a condition table, a standard buffering is set. This buffering must generally be adapted to the requirements of the installation.

Before Release 3.0, the standard buffering was either a complete buffering or no buffering. Only condition tables containing the fields, 'Customer', 'Vendor', 'Material' and 'Batch' are not buffered.

As of 3.0, a whole-status buffering is always set as standard buffering.

Please check before Release 3.0 whether you can also completely buffer the condition tables that are not buffered by default. This is possible if the tables are not changed very often (once day at the most) and if these are only minor changes (less than approx. 1000 entries).

You get access statistics per table using the SAP performance monitors (Tools -> Administration, Monitoring --> Performance, Setup/buffers --> Calls -> Execute), so that you can check the frequency of the read operations and of the table changes.

Please use the SAP Data Dictionary (transaction 13) for the complete buffering of the table by selecting "Buffering allowed" and by entering buffering type X in the technical settings. You must then activate the table.

Please observe that the normal dictionary maintenance is not used, since, in this case, this message from the transporting can appear:
TK203 'Object &1 &2 are in the reserved name area'

As of Release 3.0, a table buffered by the default settings is possibly too large. You can display the buffer quality and the storage requirement of the table in the buffer via the SAP performance monitors (Tools -> Administration, Monitoring --> Performance, Setup/buffers --> Buffers, select the line "Generic key", Buffered objects).

If the table is too large (more than 500K) and if the generic key buffer has a poor buffer quality, you can either the increase the generic key buffer (free memory required) or remove the table from the buffer by changing the technical settings of the table in the Dictionary.

After manual adaptation of a condition table, you should avoid recreation by the application.

No comments:

Post a Comment