Technical Settings
You use the technical settings of a table to define how the table is handled when it is created in the database. You can specify whether the table is buffered and whether changes to the table's data records are logged.
The most important parameters are:
- Data class:
The data class defines the physical area of the database (table space) in which the table must be created.
- Size category:
The size category defines the size of the extents created for the table.
When the table is created in the database, the system determines the required information about the memory area to be selected and the extent size from the technical settings.
- Buffering permission:
The buffering permission defines whether the table can be buffered.
- Buffering type:
If the table can be buffered, you must define a buffering type (full, generic, single-record). The buffering type defines how many table records are loaded into the buffer when a table entry is accessed.
- Logging:
This parameter defines whether the system logs changes to the table entries. If logging is switched on, the system records each change to a table record in a log table.
- Write access only with JAVA
Using the indicator "Write access with Java only" you can define that contents of the table may only be changed from within Java. If you implement changes (INSERT, UPDATE) to the table content through ABAP programs, there is no guarantee that this data can be read correctly from the Javaside. If the data written by ABAP is ASCII data, it can be read from the Java side.
- The Convert to transparent table flag ( transparent flag ) is also displayed for pooled tables or for tables which were converted into transparent tables earlier on with this flag.
See also: